[TEST] Corrosion Map Editor Validation
192.154.253.111:28025 checked 10m 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 bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
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
Quick answers
Map and rules
Which settings and rules apply on [TEST] Corrosion Map Editor Validation?
No gather rate appears in the name [TEST] Corrosion Map Editor Validation. Up to 8 players can group, which is the game's default. It runs survival, gather, build and raid: the standard game. Raiding and fighting other players are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins are running on it. Anti-cheat is off: VAC, from Valve.
Which map is active on [TEST] Corrosion Map Editor Validation?
Size 4,500, seed 1337, generated by the game: the procedural map on [TEST] Corrosion Map Editor Validation. You can view it on RustMaps from this page, since the same size and seed give the same map. Under map name you will find: Custom Map.
Population
What is the population like on [TEST] Corrosion Map Editor Validation?
The server [TEST] Corrosion Map Editor Validation is currently at 0 players out of 10 slots. Averaging 0 players over seven days, it peaked at 1. In the last two days, the peak hour was 02:00 UTC, with an average of 0 players.
What is [TEST] Corrosion Map Editor Validation's ranking?
In the top 67% of ranked servers, [TEST] Corrosion Map Editor Validation holds #14,762 for player hours over the last seven days.
Server tags
What is the meaning of the tags on [TEST] Corrosion Map Editor Validation?
What the game's server browser gets from [TEST] Corrosion Map Editor Validation is this tag list: gmrust (Game mode): Survival in the standard Rust mode; mp10 (Max players): The server has 10 slots; ts8 (Group limit): The team cap is 8, which is the game's default; v2634 (Protocol): Protocol 2634—only players on that version can get in; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, which is standard; $r? (Region code): Region code left unset; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded category: the game is altered by plugins or settings. Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.
Where does [TEST] Corrosion Map Editor Validation appear in Rust Zerg Life lists?
These Rust Zerg Life lists include [TEST] Corrosion Map Editor Validation: Modded Rust servers for clans and zergs. 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 24 hours.
Server details
What is the uptime and reliability of [TEST] Corrosion Map Editor Validation?
You can join [TEST] Corrosion Map Editor Validation now: it is online. The uptime figure it gives suggests it restarted around 9 hours ago. Its first appearance in Rust Zerg Life records is 18 October 2026.
What is the performance like on [TEST] Corrosion Map Editor Validation?
Server fps held an average of 61 for the last 48 hours, with a minimum of 50. The world held as many as 132,300 entities, including buildings, deployables and everything else. The maximum memory it used was 3,262 MB. A climbing entity count and low fps are the source of the lag players feel.
Which Rust build does [TEST] Corrosion Map Editor Validation use?
Rust network protocol 2634 and build 167781 is what [TEST] Corrosion Map Editor Validation runs, on Linux. Joining requires your game to be on the same protocol, which Steam updates automatically.
What is the location of [TEST] Corrosion Map Editor Validation?
There is no region published by [TEST] Corrosion Map Editor Validation. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 192.154.253.111:28025.
Wipe cycle
How often does [TEST] Corrosion Map Editor Validation wipe, and on what days?
So few of [TEST] Corrosion Map Editor Validation's wipes are recorded that its rhythm cannot be told yet. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it is due next. The world in play right now was made 11 hours ago.
Connect
What is the process to join [TEST] Corrosion Map Editor Validation?
You can join by opening the console with F1 and typing client.connect 192.154.253.111:28025. Or hit Launch Rust on this page to open Rust through Steam and connect.
Server tags
Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
mp10
ts8
v2634
cs167781
ptrak
$r?
Mods and access
^o
^z
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.