TST15415
test
Offline 91.108.0.219:28015 checked 40d 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 321/375
-
02COMPlayers 199/250
-
03COMPlayers 36/250
-
04COMPlayers 23/250
-
05COMPlayers 53/100
-
06COMPlayers 69/200
Quick answers
From the figures on this page.
Filters
Which lists and filters on Rust Tracker show test?
On Rust Tracker, test sits in these lists: Community servers, no tags. These filters surface it 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): Rust survival, standard mode; mp75 (Max players): Capacity: 75 slots; ts8 (Group limit): Default team size: 8; v2633 (Protocol): Your game must be on protocol 2633 to connect; cs164530 (Build): Build: 164530; ptrak (Networking): Network layer: RakNet, the game's standard; $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?
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 54 days 20 hours.
Location and Status
How reliable is test, and is it online now?
Offline: test confirmed offline, last seen 40 days 17 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. Rust Tracker logged it first on 17 September 2026.
Which Rust build is test running?
Rust network protocol 2633 and build 164530 on Linux is what test runs. The same protocol is required to join, and Steam updates it for you.
What location is test hosted in?
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 91.108.0.219:28015.
Population
How many players are on test right now?
Offline now for test, last seen 40 days 17 hours ago.
How does test compare in the rankings?
Top – of all ranked servers, and #15,415 on seven-day player hours: test.
Map and Rules
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. It runs survival, 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. VAC is on, Valve's anti-cheat.
What map is test on?
A procedural map runs on test, generated by the game.
Connect
What is the way to join test?
To connect: start Rust, press F1, enter client.connect 91.108.0.219: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 mp75,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp75
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.