TST13746
TEST
Offline 94.240.163.109:28015 checked 22d 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 62% 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 392/425
-
02COMPlayers 458/500
-
03COMPlayers 984/1000
-
04COMPlayers 56/100
-
05COMPlayers 989/1000
-
06COMPlayers 27/250
Quick answers
From the figures on this page.
Tags
Where does TEST appear in Rust Tracker lists and filters?
Community servers, no tags — the Rust Tracker lists that include TEST. 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; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167058 (Build): The game build is 167058; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Times
On what schedule 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 22 days 5 hours.
Server Details
What is the uptime on TEST, and is it online?
Tracking shows TEST offline as of now, last seen 22 days 5 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. Rust Tracker logged it first on 7 October 2026.
Which Rust version is confirmed on TEST?
Rust network protocol 2634 and build 167058 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?
Nothing on region from TEST; none is published. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 94.240.163.109:28015.
Player Count
Is TEST busy?
Offline: TEST, last seen 22 days 5 hours ago.
What rank does TEST carry among Rust servers?
Seven-day player hours put TEST at #13,746, within the top 62% of all ranked servers.
Settings
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. Raiding and PvP are permitted between players. A community server: the server browser lists it under Community. On: VAC, Valve's anti-cheat.
Which map is loaded on TEST?
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 94.240.163.109: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 mp10,ptrak,$r?,v2634,gmrust,cs167058,ts8
Game
gmrust
mp10
ts8
v2634
cs167058
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.