On the class lists: F (43), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak –
Rank#15,290top 69%
Last wipe11d 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,290 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
80/ 100
B+
Mostly smooth: 48 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
46/ 100
D
Slipped a little: down 1,209 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (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 18 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. 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
In what location does [TEST] Corrosion Map Editor Validation sit?
[TEST] Corrosion Map Editor Validation leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 192.154.253.111:28025.
How reliable is [TEST] Corrosion Map Editor Validation, and is it up?
Right now, [TEST] Corrosion Map Editor Validation is online. About 11 days 18 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 18 October 2026.
How well does [TEST] Corrosion Map Editor Validation run?
The average over the last 48 hours was 48 server fps, and it never went below 38. At its peak, it held 132,069 entities, including buildings, deployables and all else in the world. At its highest, it used 5,579 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does [TEST] Corrosion Map Editor Validation sit?
You will find [TEST] Corrosion Map Editor Validation on Rust network protocol 2634 and build 167781, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does [TEST] Corrosion Map Editor Validation wipe, and how often?
[TEST] Corrosion Map Editor Validation has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 11 days 21 hours.
Player count
Where does [TEST] Corrosion Map Editor Validation sit among Rust servers?
In the top 69% of all ranked servers, [TEST] Corrosion Map Editor Validation sits at #15,290 for player hours over the last seven days.
What does the population on [TEST] Corrosion Map Editor Validation look like?
Right now, 0 players are on [TEST] Corrosion Map Editor Validation, which has 10 slots. Over the past seven days, the average player count was 0.
Tags and filters
What is meant by the tags on [TEST] Corrosion Map Editor Validation?
The game's browser takes its cue from the tags [TEST] Corrosion Map Editor Validation has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature [TEST] Corrosion Map Editor Validation?
These Rust Server Score lists count [TEST] Corrosion Map Editor Validation among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which rules does [TEST] Corrosion Map Editor Validation enforce, and what are its settings?
You will find no gather rate in the name of [TEST] Corrosion Map Editor Validation. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server does not run VAC, Valve's anti-cheat.
Which map is in play on [TEST] Corrosion Map Editor Validation?
A procedural map of size 4,500 and seed 1337, generated by the game, is what [TEST] Corrosion Map Editor Validation runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
How to join
How should you connect to [TEST] Corrosion Map Editor Validation?
To connect, start Rust, press F1, and type client.connect 192.154.253.111:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 term to build on. Strongest in uptime (A+); population is the one to work on (F).