TST15568
TEST
Offline 98.97.136.218:28015 checked 26d 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 65% 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 440/525
-
02COMPlayers 25/250
-
03COMPlayers 45/250
-
04COMPlayers 201/275
-
05COMPlayers 76/200
-
06COMPlayers 88/150
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry TEST?
On Rust Tracker, TEST sits in these lists: 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?
Listed for the server browser to read, TEST publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp7 (Max players): Slots: 7; ts8 (Group limit): Team limit is 8, the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set. 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 Schedule
When does TEST wipe?
Too few wipes on record for TEST to show its rhythm. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. 32 days 23 hours since this world was made.
Location and Status
What is the uptime on TEST, and is it online?
Offline: TEST confirmed offline, last seen 26 days 22 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. Rust Tracker logged it first on 30 September 2026.
Which Rust version is confirmed on TEST?
Confirmed for TEST: Rust network protocol 2633 and build 164530, Windows. Steam updates it for you; your game must share the protocol to join.
Where does TEST sit?
Nothing on region from TEST; none is published. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 98.97.136.218:28015.
Population
What is the player count on TEST?
Offline now for TEST, last seen 26 days 22 hours ago.
How does TEST compare in the rankings?
Top 65% of all ranked servers, and #15,568 on seven-day player hours: TEST.
Settings
Which settings and rules are confirmed on TEST?
Nothing in TEST's name states a gather rate. 8 players per group is the game's default, and the cap holds. 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. On: VAC, Valve's anti-cheat.
What map is TEST on?
Generated by the game: the procedural map on TEST.
Connect
How do you get onto TEST?
To connect: start Rust, press F1, enter client.connect 98.97.136.218:28015 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 mp7,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp7
ts8
v2633
cs164530
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.