TST13043
test
Offline 5.175.178.27:28015 checked 45d 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 bestWipe 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 636/675
-
02COMPlayers 485/525
-
03COMPlayers 59/250
-
04COMPlayers 36/250
-
05COMPlayers 138/200
-
06COMPlayers 255/300
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry test?
Community servers, no tags — the Rust Tracker lists that include test. These filters surface it 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): Standard survival mode for Rust; mp8 (Max players): Slots: 8; ts8 (Group limit): Default team size: 8; v2633 (Protocol): Your game must be on protocol 2633 to connect; cs163794 (Build): This server runs game build 163794; ptrak (Networking): RakNet is the network layer — 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 Schedule
Which wipe times are confirmed for test?
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 45 days 23 hours.
Location and Status
Is test up, and how does its uptime hold?
Offline: test confirmed offline, last seen 45 days 1 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. The first sighting by Rust Tracker was 13 September 2026.
Which Rust build is test running?
Rust network protocol 2633 and build 163794 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?
Nothing on region from test; none is published. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 5.175.178.27:28015.
Player Count
How many players are on test right now?
Offline now for test, last seen 45 days 1 hours ago.
Where does test sit in the server rankings?
On player hours over seven days, test ranks #13,043, inside the top – of all ranked servers.
Settings
Which settings and rules are confirmed on test?
Nothing in test's name states a gather rate. 8 players per group is the game's default, and the cap holds. survival is the game mode, gather, build and raid: the standard game. Raiding and PvP are permitted between players. A community server: the server browser lists it under Community. Off: VAC, Valve's anti-cheat.
Which map is loaded on test?
Procedural map on test, made by the game.
How to Join
What is the way to join test?
To connect: start Rust, press F1, enter client.connect 5.175.178.27: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 mp8,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp8
ts8
v2633
cs163794
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.