TST11442
TEST
Offline 188.244.248.95:28015 checked 13d 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 53% 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 286/300
-
02COMPlayers 236/250
-
03COMPlayers 21/250
-
04COMPlayers 24/250
-
05COMPlayers 31/100
-
06COMPlayers 112/200
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry TEST?
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.
How should you read the tags on TEST?
Listed for the server browser to read, TEST publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Team limit is 8, the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): This server runs game build 167781; ptrak (Networking): RakNet is the network layer — 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 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 14 days 22 hours.
Server Details
How reliable is TEST, and is it online now?
Offline now, TEST was last seen 13 days 18 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. Rust Tracker logged it first on 15 October 2026.
Which Rust build is TEST running?
Confirmed for TEST: Rust network protocol 2634 and build 167781, Windows. To join, your game must be on the same protocol; Steam handles the update.
Where does TEST sit?
Nothing on region from TEST; none is published. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 188.244.248.95:28015.
Player Count
Is TEST busy?
Last seen 13 days 18 hours ago; TEST is offline at present.
Where does TEST sit in the server rankings?
Seven-day player hours put TEST at #11,442, within the top 53% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on TEST?
No gather rate appears in TEST's name. Up to 8 players per group, the game's default. It runs survival, gather, build and raid: the standard game. Fighting and raiding between players are on. A community server: the server browser lists it under Community. VAC is on, Valve's anti-cheat.
Which map is confirmed for TEST?
Generated by the game: the procedural map on TEST.
Connect
Which steps join TEST?
To connect: start Rust, press F1, enter client.connect 188.244.248.95: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,cs167781,ts8
Game
gmrust
mp10
ts8
v2634
cs167781
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.