LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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, measured since 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers, and #621 of the quad servers (top 75%). Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
mess around's wipe history is too thin on record to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. The world you are playing on was built 27 days 15 hours.
These are the Rust Live Stats lists mess around fits: Modded Rust servers live now. You will find it on the server list under Type: Modded; Game mode: Softcore; Server tag: Modded ^z and Oxide ^o; Group limit: Quad.
The server browser reads gmsoftcore (Game mode): An easier ruleset: softcore; mp10 (Max players): The slot count is 10; ts4 (Group limit): Each team holds 4 at most; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs167781 (Build): Build: 167781; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded: plugins or changed settings alter the game, which mess around publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
mess around is carrying 0 players at the moment, with 10 slots in total. The seven-day average for this server is 0 players.
On player hours for the past seven days, mess around sits at #15,338, inside the top 69% of ranked servers. Ranked against other quad servers, it comes in at #621.
Nothing in the name of mess around states a gather rate. quad sets the cap: 4 players per group. softcore applies here, An easier Facepunch mode: some loot stays yours. Fighting and raiding between players are allowed. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are in use. VAC is off: Valve's anti-cheat.
Size 4,000, seed 800000: that is the procedural map the game generates for mess around. Same size, same seed, same map: RustMaps has it, reachable from this page.
There is no region from mess around. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 157.85.86.176:23760 is its address.
The average server fps was 109 over the last 48 hours; the lowest was 92. It supported up to 86,228 entities, covering buildings, deployables and all other objects. Up to 4,430 MB of memory was used. Lag, as players feel it, comes from low fps and a rising entity count.
The setup on mess around is Rust network protocol 2635 and build 167781 with Linux. Joining requires the same protocol on your game; Steam takes care of updating it.
mess around is up and running at this moment. The uptime it reports puts the last restart at about 3 days 14 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. The first sighting by Rust Live Stats was on 1 October 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 157.85.86.176:23760.