muro_test
Offline 110.233.207.240:28015 checked 37d 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 bestBx1Wipe 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 schedule
What is the wipe schedule on muro_test?
Its rhythm cannot yet be told: too few of muro_test's wipes are on record. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 37 days 19 hours ago the server made the world it is on now.
Player counts
How busy is muro_test?
Last seen 37 days 19 hours ago, muro_test is offline at the moment.
How does muro_test rank against other Rust servers?
Ranked #15,515 on seven-day player hours, muro_test is in the top – of all ranked servers.
Settings and rules
Which map does muro_test run?
muro_test runs a procedural map, which the game generates.
What are the rules and settings on muro_test?
No gather rate appears in the name muro_test. Groups can contain up to 8 players, the default in the game. The server runs survival, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins are in use. VAC is on, which is Valve's anti-cheat.
About the server
Which version of Rust does muro_test run?
The build on muro_test is Rust network protocol 2633 and build 164530, running on Windows. Steam updates your game for you, and the protocol has to match for you to join.
Is muro_test online, and how reliable is it?
Offline at the moment: muro_test was last seen 37 days 19 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. Rust Heatmap has had it on record since 20 September 2026.
Where is muro_test located?
No region is published by muro_test. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 110.233.207.240:28015.
Tags
Which Rust Heatmap lists and filters include muro_test?
The Rust Heatmap lists that muro_test fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on muro_test mean?
gmrust (Game mode): Rust survival, standard rules; mp1 (Max players): This server has 1 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): Your game must match protocol 2633 to get in; cs164530 (Build): This build is 164530; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Settings or plugins alter the game, which puts it under Modded are the tags muro_test publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join muro_test?
To join by console, open it with F1 in Rust and enter client.connect 110.233.207.240:28015. Or press Launch Rust on this page, which connects you through Steam.