TST15481
test
Offline 140.122.178.123:28015 checked 42d 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 110/250
-
02COMPlayers 130/200
-
03COMPlayers 482/575
-
04COMPlayers 32/100
-
05COMPlayers 554/650
-
06COMPlayers 455/525
Quick answers
From the figures on this page.
Filters
Where does test appear in Rust Tracker lists and filters?
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.
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): Capacity: 10 slots; ts8 (Group limit): Default team size: 8; v2633 (Protocol): Your game must be on protocol 2633 to connect; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset. 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 Schedule
On what schedule does test wipe?
test's rhythm cannot be told yet: too few wipes on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. 43 days 8 hours since this world was made.
Location and Status
Is test up, and how does its uptime hold?
Offline now, test was last seen 42 days 11 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. First contact for Rust Tracker: 17 September 2026.
What Rust version is test on?
Confirmed for test: Rust network protocol 2633 and build 163794, Windows. The same protocol is required to join, and Steam updates it for you.
Which location is test in?
Nothing on region from test; none is published. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 140.122.178.123:28015.
Player Count
How many players are on test right now?
Offline: test, last seen 42 days 11 hours ago.
What rank does test carry among Rust servers?
On player hours over seven days, test ranks #15,481, inside the top – of all ranked servers.
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. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. A community server: the server browser lists it under Community. VAC is on, Valve's anti-cheat.
What map is test on?
Procedural map on test, made by the game.
How to Join
How do you get onto test?
Open the console in Rust with F1 after starting the game, then type client.connect 140.122.178.123:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp10
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.