Test
Offline 1.170.170.24:28015 checked 18d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What is the wipe schedule on Test?
Its rhythm cannot yet be told: too few of Test's wipes are on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 26 days 7 hours ago.
Player counts
How busy is Test?
The last time Test was seen was 18 days 10 hours ago, and it is offline now.
How does Test rank against other Rust servers?
Player hours over seven days put Test at #13,597, in the top 62% of ranked servers.
Map and rules
Which map does Test run?
A procedural map, generated by the game, runs on Test.
What are the rules and settings on Test?
No gather rate appears in the name Test. 8 players is the default group size, and that is the limit here. The server runs survival, standard play: gathering, building and raiding. Combat between players and raiding are both possible. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugin count: Oxide. VAC is on, which is Valve's anti-cheat.
Location and uptime
Which version of Rust does Test run?
Rust network protocol 2634 and build 166586 is the build Test runs, on Windows. To join, your game must match the protocol; Steam handles the update.
Is Test online, and how reliable is it?
Test is down just now; the last sighting was 18 days 10 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It first appears in Rust Heatmap records on 10 October 2026.
Where is Test located?
No region is published by Test. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. To connect, use 1.170.170.24:28015.
Lists and filters
Which Rust Heatmap lists and filters include Test?
Modded Rust servers, by live population are the Rust Heatmap lists that Test fits. Filtering the list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more brings it up.
What do the server tags on Test mean?
These are the tags Test publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp5 (Max players): Slot count: 5; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The server runs game protocol 2634, so your game has to match it; cs166586 (Build): This build is 166586; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The game is changed by settings or plugins, so it sits under Modded. The top of this page also shows the tags for players now, the queue and when the world was made.
How to join
How do I join Test?
Press F1 in Rust to open the console, then enter client.connect 1.170.170.24:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.