Rust StatisticsWorking papers on every public Rust server · 89,289 players now

[TEST] Corrosion Map Editor Validation

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 3h ago · 192.154.253.111:28025

Abstract

We describe the public Rust server [TEST] Corrosion Map Editor Validation, reached at 192.154.253.111:28025. At the last check it held 0 of 10 places, against a seven-day mean of 01. It ranks #15,323 of all servers, the top 69%. It last wiped 10d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,323top 69%
Last wipe10d agono schedule published
Next wipe3–no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123421:0006:0015:0023:0008:0017:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
02040608021:0006:0015:0023:0008:0017:00
Figure 2: 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k18 Oct20 Oct22 Oct24 Oct26 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of [TEST] Corrosion Map Editor Validation
Figure 4: The map: Custom Map, size 4500, seed 1337.
Table 3: The server's published settings.
Address192.154.253.111:28025
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe18 Oct 2026, 02:17 UTC
Hostname–
First seen18 Oct 2026
MapCustom Map
Size4500
Seed1337

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and upcoming Rust wipes [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 157 on average205/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 127 on average121/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average183/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average126/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average19/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average50/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Does [TEST] Corrosion Map Editor Validation perform well?

Over the past 48 hours, it ran at an average of 48 server fps, with a low of 29. Buildings, deployables and all other world objects counted together reached a maximum of 132,264 entities. Its highest memory usage was 5,337 MB. Players experience lag when fps is low and the entity count is rising.

A.2What is the location of [TEST] Corrosion Map Editor Validation?

There is no region published for [TEST] Corrosion Map Editor Validation. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 192.154.253.111:28025 is its address.

A.3How reliable is [TEST] Corrosion Map Editor Validation, and is it currently online?

At the present moment, [TEST] Corrosion Map Editor Validation is online. Based on the uptime it reports, the last restart occurred about 10 days 13 hours ago. Its uptime over the last full days (7 days) was 100%, with 168 of 168 hours online. It was first observed on 18 October 2026 by Rust Statistics.

A.4What version of Rust is run on [TEST] Corrosion Map Editor Validation?

Rust network protocol 2634 and build 167781 is the version that [TEST] Corrosion Map Editor Validation runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.5When are wipes carried out on [TEST] Corrosion Map Editor Validation?

Too few wipes by [TEST] Corrosion Map Editor Validation have been recorded to determine the pattern. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 10 days 17 hours ago.

Player count

A.6What is the rank of [TEST] Corrosion Map Editor Validation among Rust servers?

The seven-day player-hours ranking puts [TEST] Corrosion Map Editor Validation at #15,323, within the top 69% of ranked servers.

A.7What is the population level of [TEST] Corrosion Map Editor Validation?

The current population of [TEST] Corrosion Map Editor Validation is 0, drawn from 10 slots. The seven-day average for this server is 0 players.

Tags and filters

A.8What is the meaning of the tags on [TEST] Corrosion Map Editor Validation?

Tags from [TEST] Corrosion Map Editor Validation, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs167781 (Build): This server runs game build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can [TEST] Corrosion Map Editor Validation be found among the Rust Statistics lists and filters?

These Rust Statistics lists include [TEST] Corrosion Map Editor Validation: Modded Rust servers. It appears under the following 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.

Rules, settings, map

A.10Under what rules and settings does [TEST] Corrosion Map Editor Validation operate?

Its name carries no gather rate for [TEST] Corrosion Map Editor Validation. At 8 players, the group limit equals the game's default. survival is the game mode here; the standard mode, in which you gather, build and raid. Players may raid and fight one another. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. The server has VAC off, Valve's anti-cheat.

A.11On which map does [TEST] Corrosion Map Editor Validation take place?

Size 4,500 and seed 1337 define the procedural, game-generated map on [TEST] Corrosion Map Editor Validation. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page. Under map name, it gives Custom Map.

Connection

A.12What steps are required to join [TEST] Corrosion Map Editor Validation?

Enter client.connect 192.154.253.111:28025 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp10Max players. 10 slots are available.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Joining requires the same game version: protocol 2634.
cs167781Build. This server runs game build 167781.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.