TST12835
TEST
Offline 188.190.74.187: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 303/375
-
02COMPlayers 406/475
-
03COMPlayers 962/1000
-
04COMPlayers 44/100
-
05COMPlayers 480/8
-
06COMPlayers 986/1000
Quick answers
From the figures on this page.
Filters
Where does TEST appear in Rust Tracker lists and filters?
Community servers, no tags — the Rust Tracker lists that include TEST. 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?
These tags are published by TEST for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp10 (Max players): 10 slots on this server; ts8 (Group limit): Team limit is 8, the game default; v2633 (Protocol): To join, your game must match protocol 2633; cs163794 (Build): Build: 163794; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Schedule
When does TEST wipe?
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 9 hours.
Server Details
Is TEST up, and how does its uptime hold?
Tracking shows TEST offline as of now, last seen 45 days 3 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. First contact for Rust Tracker: 14 September 2026.
Which Rust version is confirmed on TEST?
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.
What location is TEST hosted 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 188.190.74.187:28015.
Population
Is TEST busy?
Offline now for TEST, last seen 45 days 3 hours ago.
What rank does TEST carry among Rust servers?
Top – of all ranked servers, and #12,835 on seven-day player hours: TEST.
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, raid, as the game intends. 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?
A procedural map runs on TEST, generated by the game.
How to Join
What is the way to join TEST?
Open the console in Rust with F1 after starting the game, then type client.connect 188.190.74.187: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.