TST15383
TEST
Offline 5.44.169.105: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 476/500
-
02COMPlayers 280/300
-
03COMPlayers 39/250
-
04COMPlayers 31/250
-
05COMPlayers 88/100
-
06COMPlayers 111/200
Quick answers
From the figures on this page.
Tags
Where does TEST appear in Rust Tracker lists and filters?
On Rust Tracker, TEST sits in these lists: 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?
These tags are published by TEST for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp5 (Max players): Slots: 5; ts8 (Group limit): Default team size: 8; v2633 (Protocol): To join, your game must match protocol 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): The region code is unset. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Times
On what schedule 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. 40 days 21 hours since this world was made.
Location and Status
Is TEST up, and how does its uptime hold?
Tracking shows TEST offline as of now, last seen 40 days 9 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. The first sighting by Rust Tracker was 18 September 2026.
Which Rust version is confirmed on TEST?
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.
Where does TEST sit?
No region is published by TEST. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 5.44.169.105:28015.
Population
Is TEST busy?
Last seen 40 days 9 hours ago; TEST is offline at present.
How does TEST compare in the rankings?
Top – of all ranked servers, and #15,383 on seven-day player hours: TEST.
Settings
Which settings and rules are confirmed on TEST?
No gather rate appears in TEST's name. 8 players per group is the game's default, and the cap holds. 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. 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 5.44.169.105: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.