[TEST] Corrosion Map Editor Validation
Online 192.154.253.111:28025 checked 7m ago
Server instruments
last reading Wed 20:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 29 · below 20 is lag, below 10 is badEntities
48 h range 129,826–132,264 · memory 4,942 MBUptime
10 days 16 hours since its last restart, at the last readingPlayers
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 | 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
the same kind of game, then region, group limit, rate and wipes- 105/500
- 129/100
- 119/225
- 90/700
- 25/200
- 24/1000
Quick answers
from the figures on this pageWipe timing
What wipe timing does [TEST] Corrosion Map Editor Validation follow?
To tell the rhythm of [TEST] Corrosion Map Editor Validation, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 10 days 19 hours ago.
Tag meanings
Which tags does [TEST] Corrosion Map Editor Validation carry, and what do they mean?
Tags published by [TEST] Corrosion Map Editor Validation, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does [TEST] Corrosion Map Editor Validation appear in Rust Metrics lists and filters?
These Rust Metrics lists carry [TEST] Corrosion Map Editor Validation: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Occupancy
Where does [TEST] Corrosion Map Editor Validation sit in the rankings?
Ranking for [TEST] Corrosion Map Editor Validation: #15,348 on seven-day player hours, top 69% of all ranked servers.
How full does [TEST] Corrosion Map Editor Validation get?
0 of 10 slots are filled on [TEST] Corrosion Map Editor Validation right now. Check: player average. 0 over the last seven days.
Server details
What location is [TEST] Corrosion Map Editor Validation hosted in?
No region comes from [TEST] Corrosion Map Editor Validation. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 192.154.253.111:28025.
What Rust version is [TEST] Corrosion Map Editor Validation on?
Reading: [TEST] Corrosion Map Editor Validation, Rust network protocol 2634 and build 167781, Linux. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for [TEST] Corrosion Map Editor Validation?
Over the last 48 hours the average was 48 server fps; the floor was 29. Peak entity count: 132,264. Buildings, deployables and all else included. Reading: 5,337 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on [TEST] Corrosion Map Editor Validation, and is it online?
[TEST] Corrosion Map Editor Validation reports online. Status: normal. By its reported uptime, the last restart was roughly 10 days 16 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. The first sighting on Rust Metrics was 18 October 2026.
Rules and settings
What rules does [TEST] Corrosion Map Editor Validation enforce, and what are its settings?
Reading the name gives no gather rate for [TEST] Corrosion Map Editor Validation. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC off, Valve's system.
What map is [TEST] Corrosion Map Editor Validation on?
From seed 1337, the game generates the procedural map on [TEST] Corrosion Map Editor Validation. Its size is 4,500. The map repeats when size and seed match. Open it on RustMaps from this page. Read the map name: Custom Map.
Connection
How do you connect to [TEST] Corrosion Map Editor Validation?
Check: join. Open Rust, press F1, then enter client.connect 192.154.253.111:28025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.