Station XX-15411 · recording
[TEST] Corrosion Map Editor Validation
Online 192.154.253.111:28025 checked 14m ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,411
- top 69%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M0.0■steady+0 players
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, measured since 18 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on [TEST] Corrosion Map Editor Validation?
[TEST] Corrosion Map Editor Validation runs a procedural map of size 4,500 with seed 1337, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page. The name of its map is Custom Map.
Which settings and rules apply on [TEST] Corrosion Map Editor Validation?
The name of [TEST] Corrosion Map Editor Validation gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Anti-cheat is off: VAC, from Valve.
Live population
How many players are recorded on [TEST] Corrosion Map Editor Validation right now?
0 of the 10 slots on [TEST] Corrosion Map Editor Validation are filled right now. Averaged across the last seven days, the population was 0 players.
How does [TEST] Corrosion Map Editor Validation rank against other Rust servers?
Over the last seven days, [TEST] Corrosion Map Editor Validation recorded enough player hours to reach #15,411 worldwide, placing it in the top 69% of all ranked servers.
Server facts
How reliably does [TEST] Corrosion Map Editor Validation stay online?
[TEST] Corrosion Map Editor Validation is up at the moment. Going by the uptime figure it reports, it restarted about 10 days 7 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. On 18 October 2026 it was recorded for the first time by Rust Server Trends.
How well does [TEST] Corrosion Map Editor Validation perform under load?
The 48-hour average is 48 server fps; 29 is the lowest observed. The world held up to 132,264 entities at its peak, buildings and deployables included. Its highest memory use was 5,337 MB. What you feel as lag is the combination of low fps and a rising entity count.
Which region does [TEST] Corrosion Map Editor Validation run from?
Nothing about a region comes from [TEST] Corrosion Map Editor Validation. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 192.154.253.111:28025 is the address it uses.
What build of Rust does [TEST] Corrosion Map Editor Validation use?
Rust network protocol 2634 and build 167781 on Linux is what [TEST] Corrosion Map Editor Validation runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
How often does [TEST] Corrosion Map Editor Validation wipe, and on which days?
Too few wipes of [TEST] Corrosion Map Editor Validation are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 10 days 9 hours.
Tags
What do the server tags on [TEST] Corrosion Map Editor Validation mean?
These are the tags [TEST] Corrosion Map Editor Validation publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): Game build: 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does [TEST] Corrosion Map Editor Validation appear?
You will find [TEST] Corrosion Map Editor Validation on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters 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.
Join the server
How do you connect to [TEST] Corrosion Map Editor Validation?
To join, enter client.connect 192.154.253.111:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.