TST15973
test
Offline 77.48.47.4:28015 checked 26d 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 70% 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 169/250
-
02COMPlayers 108/200
-
03COMPlayers 16/250
-
04COMPlayers 15/250
-
05COMPlayers 16/100
-
06COMPlayers 21/200
Quick answers
From the figures on this page.
Filters
Where does test appear in Rust Tracker lists and filters?
On Rust Tracker, test sits in these lists: 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.
What do the tags mean that test is listed under?
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): Default team size: 8; v2634 (Protocol): Join only if your game is on protocol 2634; cs166586 (Build): The game build is 166586; ptrak (Networking): RakNet is the network layer — 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 Schedule
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. Its world went live 26 days 11 hours.
Location and Status
Is test up, and how does its uptime hold?
Offline: test confirmed offline, last seen 26 days 5 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. The first sighting by Rust Tracker was 2 October 2026.
Which Rust build is test running?
Rust network protocol 2634 and build 166586 on Windows is what test runs. Steam updates it for you; your game must share the protocol to join.
Where does test sit?
No region is 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 77.48.47.4:28015.
Population
How many players are on test right now?
Offline: test, last seen 26 days 5 hours ago.
What rank does test carry among Rust servers?
Top 70% of all ranked servers, and #15,973 on seven-day player hours: test.
Map and Rules
Which settings and rules are confirmed on test?
The name of test carries no gather rate. 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. Listed under Community in the server browser, it is a community server. Off: VAC, Valve's anti-cheat.
What map is test on?
A procedural map runs on test, generated by the game.
Connect
Which steps join test?
Open the console in Rust with F1 after starting the game, then type client.connect 77.48.47.4: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,cs166586,ts8
Game
gmrust
mp10
ts8
v2634
cs166586
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.