muro_test
Offline 110.233.207.240:28015 checked 27d 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
- 963/ 100
- 145/ 400
- 117/ 245
- 120/ 100
- 338/ 1000
- 22/ 700
Quick answers
Tags and filters
Where does muro_test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry muro_test are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on muro_test?
gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): It holds 1 players; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): To join, your game has to be on protocol 2633; cs164530 (Build): It's on build 164530; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play — that is the tag list muro_test puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What's the location of muro_test?
No region comes from muro_test. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 110.233.207.240:28015.
How reliable is muro_test?
The server muro_test is not reachable at the moment; the last sighting was 27 days 7 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 20 September 2026.
What Rust version is muro_test on?
The version on muro_test is Rust network protocol 2633 and build 164530, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
How often does muro_test wipe?
muro_test's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. The world you are on now was created 27 days 7 hours.
Settings and map
What settings and rules have been applied to muro_test?
Its name does not state a gather rate for muro_test. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
Which map is active on muro_test?
A procedural map, generated by the game, is in play on muro_test.
Player count
Is muro_test busy?
The last sighting of muro_test was 27 days 7 hours ago; it is offline right now.
What's muro_test's rank among Rust servers?
Over the last seven days, muro_test is #15,515 by player hours, among the top – of all ranked servers.
Join info
What's the way to join muro_test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 110.233.207.240:28015.