TST12454
TEST
Offline 95.24.109.157:28015 checked 6d 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 56% 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 141/250
-
02COMPlayers 115/200
-
03COMPlayers 14/250
-
04COMPlayers 19/250
-
05COMPlayers 11/100
-
06COMPlayers 18/200
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry TEST?
These Rust Tracker lists carry TEST: 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; Last wipe: In the last week.
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): 10 slots on this server; ts8 (Group limit): Team limit is 8, the game default; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): Build: 167781; ptrak (Networking): Network layer: RakNet, the game's standard; $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
When does TEST wipe?
Too few wipes on record for TEST to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. This world has been running 6 days 11 hours.
Location and Status
What is the uptime on TEST, and is it online?
Offline: TEST confirmed offline, last seen 6 days 11 hours ago. Uptime stood at 0% for the last 6 full days, 0 of 144 hours online. Rust Tracker logged it first on 22 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.
Which location is TEST in?
Region: none published by TEST. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 95.24.109.157:28015.
Population
Is TEST busy?
Offline now for TEST, last seen 6 days 11 hours ago. Seven-day average 1 players; peak 1.
How does TEST compare in the rankings?
Top 56% of all ranked servers, and #12,454 on seven-day player hours: TEST.
Map and Rules
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 and raid: the standard game. Players can raid and fight each other here. A community server: the server browser lists it under Community. On: VAC, Valve's anti-cheat.
Which map is loaded on TEST?
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 95.24.109.157:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
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.