TST15426
test
Offline 2.127.215.235:28015 checked 43d 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 bestWipe 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 164/250
-
02COMPlayers 170/200
-
03COMPlayers 18/250
-
04COMPlayers 15/250
-
05COMPlayers 14/100
-
06COMPlayers 76/200
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry test?
These Rust Tracker lists carry test: Community servers, no tags. It comes up under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which tags does test carry, and what do they mean?
Listed for the server browser to read, test publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Default team size: 8; v2633 (Protocol): To join, your game must match protocol 2633; cs163794 (Build): This server runs game build 163794; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Times
Which wipe times are confirmed for test?
Too few wipes on record for test to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. Its world went live 44 days 13 hours.
Server Details
How reliable is test, and is it online now?
Tracking shows test offline as of now, last seen 43 days 17 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. First contact for Rust Tracker: 14 September 2026.
Which Rust build is test running?
Rust network protocol 2633 and build 163794 on Windows is what test runs. Steam updates it for you; your game must share the protocol to join.
Which location is test in?
Nothing on region from test; none is published. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 2.127.215.235:28015.
Player Count
Is test busy?
Offline now for test, last seen 43 days 17 hours ago.
How does test compare in the rankings?
On player hours over seven days, test ranks #15,426, inside the top – of all ranked servers.
Settings
Which settings and rules are confirmed on test?
The name of test carries no gather rate. Up to 8 players per group, the game's default. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. Listed under Community in the server browser, it is a community server. VAC is on, Valve's anti-cheat.
Which map is loaded on test?
A procedural map runs on test, generated by the game.
Connect
What is the way to join test?
Open the console in Rust with F1 after starting the game, then type client.connect 2.127.215.235:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp100,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp100
ts8
v2633
cs163794
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.