On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak –
Rank#15,351top 69%
Last wipe27d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,351 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 110 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 389 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers, and #624 of the quad servers (top 75%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe 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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for mess around. Rust Server Score takes the server's word for its location and does not trace the hardware. 157.85.86.176:23760 is the address to use.
How dependable is mess around, and is it online at the moment?
The server is up: mess around is online now. About 3 days 9 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 1 October 2026.
Does mess around perform well?
It never fell below 92 server fps in the last 48 hours, averaging 110. Up to 86,228 entities were in the world, covering buildings, deployables and the rest. Up to 4,175 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is mess around running?
Rust network protocol 2635 and build 167781 on Linux is what mess around runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does mess around wipe its map?
The record holds too few of mess around's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 27 days 10 hours.
Player numbers
Where does mess around sit among Rust servers?
In the top 69% of all ranked servers, mess around sits at #15,351 for player hours over the last seven days. It comes #624 among servers in the quad group.
What does the population on mess around look like?
With 10 slots available, mess around currently has 0 players. Over the past seven days, the average player count was 0.
Tags
How should you read the tags on mess around?
You'll see mess around tagged with gmsoftcore (Game mode): An easier ruleset, softcore; mp10 (Max players): Its slot count is 10; ts4 (Group limit): No team may go above 4; v2635 (Protocol): Join only if your game runs protocol 2635; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show mess around?
These Rust Server Score lists count mess around among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: Softcore; Server tag: Modded ^z and Oxide ^o; Group limit: Quad.
Server rules
Which rules does mess around enforce, and what are its settings?
Nothing in the name of mess around states a gather rate. The cap on group size is 4 players (quad). softcore is the mode here, Facepunch's gentler mode: part of your loot stays with you. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server does not run VAC, Valve's anti-cheat.
mess around runs which map?
A procedural map of size 4,000 and seed 800000, generated by the game, is what mess around runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto mess around?
To connect, start Rust, press F1, and type client.connect 157.85.86.176:23760. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmsoftcore,cs167781,ts4,^o^z
Game
gmsoftcore
Game modeAn easier ruleset, softcore.
mp10
Max playersIts slot count is 10.
ts4
Group limitNo team may go above 4.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).