TST15962
test
Offline 78.39.13.35:28015 checked 24d 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 71% 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 303/375
-
02COMPlayers 394/475
-
03COMPlayers 952/1000
-
04COMPlayers 42/100
-
05COMPlayers 480/8
-
06COMPlayers 981/1000
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show test?
These Rust Tracker lists carry test: Community servers, no tags. On the server list, these filters bring it up: 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): Rust survival, standard mode; mp20 (Max players): Capacity: 20 slots; ts8 (Group limit): Default team size: 8; v2633 (Protocol): To join, your game must match protocol 2633; cs165217 (Build): Build: 165217; ptrak (Networking): Network layer is RakNet, which is standard for the game; $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 Schedule
Which wipe times are confirmed for test?
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. 35 days 1 hours since this world was made.
Location and Status
Is test up, and how does its uptime hold?
Tracking shows test offline as of now, last seen 24 days 5 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. The first sighting by Rust Tracker was 5 October 2026.
Which Rust build is test running?
Confirmed for test: Rust network protocol 2633 and build 165217, Windows. Steam updates it for you; your game must share the protocol to join.
What location is test hosted in?
Region: none published by test. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 78.39.13.35:28015.
Population
How many players are on test right now?
Offline: test, last seen 24 days 5 hours ago.
What rank does test carry among Rust servers?
On player hours over seven days, test ranks #15,962, inside the top 71% of all ranked servers.
Map and Rules
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. survival is the game mode, 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. On: VAC, Valve's anti-cheat.
What map is test on?
Procedural map on test, made by the game.
Connect
How do you get onto test?
To connect: start Rust, press F1, enter client.connect 78.39.13.35: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 mp20,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp20
ts8
v2633
cs165217
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.