TST14509
TEST
Offline 185.176.113.147:28015 checked 42d 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 291/300
-
02COMPlayers 269/250
-
03COMPlayers 24/250
-
04COMPlayers 21/250
-
05COMPlayers 39/100
-
06COMPlayers 125/200
Quick answers
From the figures on this page.
Filters
Which lists and filters on Rust Tracker show TEST?
On Rust Tracker, TEST sits in these lists: 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.
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): Standard survival mode for Rust; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2633 (Protocol): To join, your game must match protocol 2633; cs164541 (Build): The game build is 164541; ptrak (Networking): Network layer: RakNet, 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
When does TEST wipe?
The record holds too few of TEST's wipes to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. 42 days 12 hours since this world was made.
Server Details
How reliable is TEST, and is it online now?
Offline: TEST confirmed offline, last seen 42 days 12 hours ago. Uptime stood at 0% for the last 7 full days, 0 of 168 hours online. The first sighting by Rust Tracker was 16 September 2026.
Which Rust version is confirmed on TEST?
Rust network protocol 2633 and build 164541 is the build on TEST; the platform is Windows. 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 185.176.113.147:28015.
Player Count
Is TEST busy?
Offline now for TEST, last seen 42 days 12 hours ago.
What rank does TEST carry among Rust servers?
Seven-day player hours put TEST at #14,509, within the top – of all ranked servers.
Settings
Which settings and rules are confirmed on TEST?
No gather rate appears in TEST's name. The game's default applies: groups can have up to 8 players. survival is the game mode, gather, build, raid, as the game intends. Fighting and raiding between players are on. The server browser lists it under Community, as a community server. On: 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 185.176.113.147:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs164541,ts8
Game
gmrust
mp10
ts8
v2633
cs164541
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.