Offline 142.117.33.159:28015 checked 11d ago
CorrosiveMods Local Development
Connect
srv = rust.server("142.117.33.159:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 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)| wiped | peak | crowd | lasted | players_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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 142.117.33.159:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 19:49 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)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 19/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 32/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 6/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 21/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 114/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does CorrosiveMods Local Development rank?
Over the last seven days CorrosiveMods Local Development sits at #15,248 on player hours, in the top 69% of ranked servers.
What population does CorrosiveMods Local Development carry?
CorrosiveMods Local Development returns no live count at this refresh, having last been seen 11 days 5 hours ago.
Server data
Which Rust version is CorrosiveMods Local Development on?
Rust network protocol 2634 and build 167781 on Windows is what CorrosiveMods Local Development runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is CorrosiveMods Local Development, and is it up?
The latest sample has CorrosiveMods Local Development offline, with a last sighting 11 days 5 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 18 October 2026.
In which location is CorrosiveMods Local Development hosted?
No region is published by CorrosiveMods Local Development. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 142.117.33.159:28015 is its address.
Rules, settings, map
What rules and settings are recorded for CorrosiveMods Local Development?
No gather rate appears in the name: CorrosiveMods Local Development. No custom cap; the default of 8 players per group stands. Recorded as survival, 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. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has CorrosiveMods Local Development selected?
A procedural map runs on CorrosiveMods Local Development, generated by the game.
Wipe schedule
On what schedule does CorrosiveMods Local Development wipe?
Too few wipes are on record for CorrosiveMods Local Development to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 11 days 7 hours ago, and that is the one in play.
Lists and tags
Where does CorrosiveMods Local Development appear among Rust Data lists and filters?
The Rust Data lists that CorrosiveMods Local Development fits are: Modded Rust servers. 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 2 weeks.
How should you read the server tags on CorrosiveMods Local Development?
The game's server browser reads these tags from CorrosiveMods Local Development: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): 4 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to CorrosiveMods Local Development?
Enter client.connect 142.117.33.159:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.