TST13159
test
Offline 217.142.18.79:20000 checked 7d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
-
01COMPlayers 486/525
-
02COMPlayers 401/450
-
03COMPlayers 52/250
-
04COMPlayers 44/250
-
05COMPlayers 48/100
-
06COMPlayers 161/200
Quick answers
From the figures on this page.
Filters
Which lists and filters on Rust Tracker show test?
These Rust Tracker lists carry test: Community servers, no tags. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on test?
The game's server browser reads these tags from test: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): 10 slots on this server; ts8 (Group limit): Team limit is 8, the game default; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167781 (Build): This server runs game build 167781; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): The region code is unset. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.
Wipe Times
When does test wipe?
test's rhythm cannot be told yet: too few wipes on record. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. This world has been running 26 days 18 hours.
Location and Status
Is test up, and how does its uptime hold?
Offline now, test was last seen 7 days 17 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. Rust Tracker logged it first on 21 October 2026.
Which Rust build is test running?
Rust network protocol 2634 and build 167781 is the build on test; the platform is Windows. The same protocol is required to join, and Steam updates it for you.
Where does test sit?
Region: none published by test. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 217.142.18.79:20000.
Population
What is the player count on test?
Last seen 7 days 17 hours ago; test is offline at present.
What rank does test carry among Rust servers?
Top 59% of all ranked servers, and #13,159 on seven-day player hours: test.
Map and Rules
Which settings and rules are confirmed on test?
No gather rate appears in test's name. Up to 8 players per group, the game's default. survival is the game mode, gather, build, raid, as the game intends. Fighting and raiding between players are on. The server browser lists it under Community, as a community server. Off: VAC, Valve's anti-cheat.
Which map is confirmed for test?
Generated by the game: the procedural map on test.
How to Join
What is the way to join test?
To connect: start Rust, press F1, enter client.connect 217.142.18.79:20000 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
mp10
ts8
v2634
cs167781
ptrak
$r?
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.