TST15092
test
Offline 9.246.41.114:20000 checked 16d 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 69% 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 410/500
-
02COMPlayers 274/300
-
03COMPlayers 40/250
-
04COMPlayers 35/250
-
05COMPlayers 76/100
-
06COMPlayers 92/200
Quick answers
From the figures on this page.
Filters
Which lists and filters on Rust Tracker show 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.
How should you read the tags on test?
These tags are published by test for the game's server browser to read: 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): Join only if your game is on protocol 2634; cs167584 (Build): Build: 167584; ptrak (Networking): Network layer: RakNet, 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. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. 26 days 4 hours since this world was made.
Location and Status
How reliable is test, and is it online now?
Offline: test confirmed offline, last seen 16 days 10 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. Rust Tracker logged it first on 12 October 2026.
What Rust version is test on?
Rust network protocol 2634 and build 167584 on Windows is what test runs. Steam updates it for you; your game must share the protocol to join.
What location is test hosted in?
Region: none published by test. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 9.246.41.114:20000.
Population
How many players are on test right now?
Offline: test, last seen 16 days 10 hours ago.
What rank does test carry among Rust servers?
Seven-day player hours put test at #15,092, within the top 69% of all ranked servers.
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 and raid: the standard game. Raiding and PvP are permitted between players. The server browser lists it under Community, as a community server. Off: 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?
To connect: start Rust, press F1, enter client.connect 9.246.41.114: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,cs167584,ts8
Game
gmrust
mp10
ts8
v2634
cs167584
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.