TST15882
test
Offline 145.224.72.110:20000 checked 19d 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 72% 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 523/525
-
02COMPlayers 385/450
-
03COMPlayers 48/250
-
04COMPlayers 51/250
-
05COMPlayers 54/100
-
06COMPlayers 161/200
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry test?
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.
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; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167398 (Build): This server runs game build 167398; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Times
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. Its world went live 26 days 18 hours.
Location and Status
What is the uptime on test, and is it online?
Offline now, test was last seen 19 days 18 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. Rust Tracker logged it first on 9 October 2026.
Which Rust build is test running?
Confirmed for test: Rust network protocol 2634 and build 167398, Windows. The same protocol is required to join, and Steam updates it for you.
Which location is test in?
No region is published by test. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 145.224.72.110:20000.
Player Count
Is test busy?
Last seen 19 days 18 hours ago; test is offline at present.
How does test compare in the rankings?
Seven-day player hours put test at #15,882, within the top 72% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on test?
Nothing in test's name states a gather rate. Up to 8 players per group, the game's default. It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. A community server: the server browser lists it under Community. Off: VAC, Valve's anti-cheat.
Which map is loaded on test?
Generated by the game: the procedural map on test.
How to Join
How do you get onto test?
To connect: start Rust, press F1, enter client.connect 145.224.72.110:20000 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 mp10,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
mp10
ts8
v2634
cs167398
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.