Rust PopulationField survey · Rust servers
Observing 38,808 players 11,700 servers 2,943 with someone on 91 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 13,052habitat unknownfirst seen 19 Sep 2026

TestServ

Offline 5.68.240.132:28015 checked 10d ago

Measurements

Players now
1/ 500
= 1 player
0% full
7-day average
0
peak –
Rank
#13,052
top 59%
Last wipe
24d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

This server has not answered a direct query in the last 48 hours.

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct11 Oct18 Oct25 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

Obs. 4 · the wipe cycle

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

2.6 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 9 OctSun 4 OctSat 3 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 04:15 UTC19d ago 1 – running 1
Sun 4 Oct, 06:16 UTC24d ago 1 held half 4.9 days 0
Sat 3 Oct, 21:52 UTC25d ago 1 – 0.4 days 1

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Field questions

Quick answers

from the figures on this page

Population

How does TestServ rank against other Rust servers?

By player hours over the last seven days, TestServ places at #13,052, within the top 59% of ranked servers.

How busy is TestServ?

At this count TestServ is offline, with its last sighting 10 days 16 hours ago.

Tags

What do the server tags on TestServ mean?

The game's server browser reads the tags TestServ publishes: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): The server has 500 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code is left blank. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.

Which Rust Population lists and filters include TestServ?

On Rust Population, TestServ is filed under these lists: Community servers, field-listed. Look for it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Wipe schedule

What does wipe day look like on TestServ?

Across its recent wipes the busiest crowds averaged 1 players. 0 hours after the latest wipe the crowd peaked. In 100% of recent wipes, half the peak was held until the next wipe.

What is the wipe schedule on TestServ?

Irregular times are when TestServ wipes, which leaves no next wipe to predict. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 24 days 15 hours ago.

Settings

Which map does TestServ run?

A procedural map, generated by the game, is in use on TestServ.

What are the rules and settings on TestServ?

The name tells you nothing about gather rates: TestServ states none. No limit is set beyond the standard 8 players per group. survival is what it runs, raid, build and gather: the standard game. Fighting and raiding between players is allowed. The server browser lists it under Community, as a community server. The anti-cheat VAC from Valve is enabled.

About the server

Which version of Rust does TestServ run?

Rust network protocol 2634 and build 167781 on Windows is what TestServ uses. Your game needs the same protocol to join; Steam takes care of updating it.

Is TestServ online, and how reliable is it?

Offline at the moment, TestServ was last seen 10 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. The first sighting by Rust Population was on 19 September 2026.

Where is TestServ located?

Nothing published by TestServ states a region. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 5.68.240.132:28015.

Getting in

How do I join TestServ?

Open the console with F1 in Rust and enter client.connect 5.68.240.132:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp500
Max players The server has 500 slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2634
Protocol Your game needs the same version, protocol 2634, to join.
cs167781
Build The game build is 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code is left blank.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.