test
Offline 5.164.252.134:28015 checked 29d 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 68% 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?
The record of test's wipes is not yet long enough to show a rhythm. 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 29 days 18 hours ago.
Population
How busy is test?
Last seen 29 days 17 hours ago, test is offline at the moment.
How does test rank against other Rust servers?
Player hours over seven days put test at #16,247, in the top 68% of ranked servers.
Rules and settings
Which map does test run?
test runs a procedural map, which the game generates.
What are the rules and settings on test?
The name test does not specify a gather rate. The group limit is 8 players, which is the game's default. survival is the game mode, 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: Carbon. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does test run?
Rust network protocol 2634 and build 166016 is the build test runs, on Windows. Your game must run the same protocol to join, and Steam takes care of updating it.
Is test online, and how reliable is it?
test is down just now; the last sighting was 29 days 17 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. Rust Heatmap has had it on record since 28 September 2026.
Where is test located?
No region is published by test. Rust Heatmap shows the location a server states. It does not look up the machine's location. To connect, use 5.164.252.134:28015.
Lists and filters
Which Rust Heatmap lists and filters include test?
These Rust Heatmap lists include test: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
What do the server tags on test mean?
The game's server browser reads the tags test publishes: gmrust (Game mode): Survival in the standard Rust form; mp15 (Max players): This server has 15 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): The server runs game protocol 2634, so your game has to match it; cs166016 (Build): This build is 166016; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
How to join
How do I join test?
Press F1 in Rust to open the console, then enter client.connect 5.164.252.134:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.