Rust Data

rustdata.spaceservers192.154.253.111:28027.ipynb

Run all rust-data · live

‹ All servers

Online 192.154.253.111:28025 checked 10m ago

[TEST] Corrosion Map Editor Validation

moddedoxide

Connect

srv = rust.server("192.154.253.111:28027")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,339 # top 69%
last wipe 10d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608023:0008:0017:0002:0011:0021:00

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k18 Oct20 Oct22 Oct24 Oct26 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

srv.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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

4500 · seed 1337
Map of [TEST] Corrosion Map Editor Validation
map
Custom Map
size
4500
seed
1337

Server

srv.info()
address
192.154.253.111:28025
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
18 Oct 2026, 02:17 UTC
hostname
–
first seen
18 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average74/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average127/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average72/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 91 on average58/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average18/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average9/1000

Quick answers

From the figures on this page.

Population data

How does [TEST] Corrosion Map Editor Validation compare in the rankings?

Rank #15,339 on seven-day player hours for [TEST] Corrosion Map Editor Validation, within the top 69% of all ranked servers.

How full does [TEST] Corrosion Map Editor Validation run?

[TEST] Corrosion Map Editor Validation reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players.

Server facts

How well does [TEST] Corrosion Map Editor Validation perform?

The 48-hour average is 48 server fps, with a low of 29. Buildings, deployables and all else in the world took the count as high as 132,264 entities. Memory peaked at 5,337 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does [TEST] Corrosion Map Editor Validation run?

Rust network protocol 2634 and build 167781 on Linux is what [TEST] Corrosion Map Editor Validation runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is [TEST] Corrosion Map Editor Validation, and is it up?

[TEST] Corrosion Map Editor Validation reports itself online at the current refresh. Count back 10 days 17 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 18 October 2026.

In which location is [TEST] Corrosion Map Editor Validation hosted?

There is no region published for [TEST] Corrosion Map Editor Validation. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 192.154.253.111:28025.

Map and rules

Which rules apply on [TEST] Corrosion Map Editor Validation, and what settings?

No gather rate appears in the name: [TEST] Corrosion Map Editor Validation. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is not running; Valve's anti-cheat is off.

What is the map on [TEST] Corrosion Map Editor Validation?

[TEST] Corrosion Map Editor Validation runs a procedural map of size 4,500 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.

Wipe schedule

On what schedule does [TEST] Corrosion Map Editor Validation wipe?

The record for [TEST] Corrosion Map Editor Validation holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 10 days 20 hours ago.

Tags and filters

Which lists on Rust Data hold [TEST] Corrosion Map Editor Validation, and which filters?

These Rust Data lists include [TEST] Corrosion Map Editor Validation: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on [TEST] Corrosion Map Editor Validation?

These tags are published by [TEST] Corrosion Map Editor Validation and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to [TEST] Corrosion Map Editor Validation?

The manual route: launch Rust, F1, then client.connect 192.154.253.111:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167781
Build Build number: 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits 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.

Rust Data 60,085 players 11,768 servers online