TST14087
TEST
Offline 87.248.191.79:28015 checked 33d 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 61% 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 555/625
-
02COMPlayers 411/450
-
03COMPlayers 175/250
-
04COMPlayers 53/100
-
05COMPlayers 178/250
-
06COMPlayers 346/225
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. 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.
Which tags does TEST carry, and what do they mean?
The game's server browser reads these tags from TEST: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): Slots: 10; ts8 (Group limit): Default team size: 8; v2633 (Protocol): To join, your game must match protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer is RakNet, which is standard for the game; $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 Times
On what schedule does TEST wipe?
Too few wipes on record for TEST to show its rhythm. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. Its world went live 35 days 17 hours.
Location and Status
Is TEST up, and how does its uptime hold?
Offline now, TEST was last seen 33 days 16 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. The first sighting by Rust Tracker was 23 September 2026.
Which Rust build is TEST running?
Rust network protocol 2633 and build 165217 on Windows is what TEST runs. To join, your game must be on the same protocol; Steam handles the update.
Which location is TEST 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. You connect at 87.248.191.79:28015.
Player Count
Is TEST busy?
Last seen 33 days 16 hours ago; TEST is offline at present.
How does TEST compare in the rankings?
Top 61% of all ranked servers, and #14,087 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. The server browser lists it under Community, as a community server. VAC is on, Valve's anti-cheat.
What map is TEST on?
A procedural map runs on TEST, generated by the game.
How to Join
Which steps join TEST?
To connect: start Rust, press F1, enter client.connect 87.248.191.79: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?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp10
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.