TST14101
test
Offline 88.204.55.228:28015 checked 39d 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 149/250
-
02COMPlayers 119/200
-
03COMPlayers 13/250
-
04COMPlayers 22/250
-
05COMPlayers 12/100
-
06COMPlayers 23/200
Quick answers
From the figures on this page.
Tags
Where does test appear in Rust Tracker lists and filters?
These Rust Tracker lists carry test: 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.
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; mp5 (Max players): 5 slots on this server; ts8 (Group limit): Default team size: 8; 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): No region code is set. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Schedule
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. This world has been running 39 days 17 hours.
Server Details
How reliable is test, and is it online now?
Tracking shows test offline as of now, last seen 39 days 14 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. Rust Tracker logged it first on 19 September 2026.
What Rust version is test on?
Rust network protocol 2633 and build 164530 on Windows is what test runs. The same protocol is required to join, and Steam updates it for you.
What location is test hosted in?
Region: none published by test. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 88.204.55.228:28015.
Population
Is test busy?
Offline: test, last seen 39 days 14 hours ago.
Where does test sit in the server rankings?
Top – of all ranked servers, and #14,101 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. The game's default applies: groups can have up to 8 players. It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. Listed under Community in the server browser, it is a community server. On: VAC, Valve's anti-cheat.
Which map is confirmed for test?
A procedural map runs on test, generated by the game.
How to Join
What is the way to join test?
Open the console in Rust with F1 after starting the game, then type client.connect 88.204.55.228:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp5,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp5
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.