TST15488
TEST
Offline 185.119.0.41: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 395/500
-
02COMPlayers 246/300
-
03COMPlayers 42/250
-
04COMPlayers 31/250
-
05COMPlayers 70/100
-
06COMPlayers 81/200
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry TEST?
These Rust Tracker lists carry TEST: 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.
How should you read the tags on TEST?
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; v2633 (Protocol): Join only if your game is on protocol 2633; cs163794 (Build): Build: 163794; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset. 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
On what schedule does TEST wipe?
The record holds too few of TEST's wipes to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. 43 days 9 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 42 days 6 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. The first sighting by Rust Tracker was 15 September 2026.
Which Rust version is confirmed on TEST?
Rust network protocol 2633 and build 163794 is the build on TEST; the platform is Windows. The same protocol is required to join, and Steam updates it for you.
What location is TEST hosted in?
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. You connect at 185.119.0.41:28015.
Population
Is TEST busy?
Offline now for TEST, last seen 42 days 6 hours ago.
Where does TEST sit in the server rankings?
Top – of all ranked servers, and #15,488 on seven-day player hours: TEST.
Map and Rules
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. Players can raid and fight each other here. The server browser lists it under Community, as a community server. VAC is on, Valve's anti-cheat.
Which map is loaded on TEST?
Procedural map on TEST, made by the game.
Connect
Which steps join TEST?
Open the console in Rust with F1 after starting the game, then type client.connect 185.119.0.41: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,cs163794,ts8
Game
gmrust
mp10
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.