Offline 67.161.116.223:28015 checked 25d ago
Corrosion Hour Development Test Server
Connect
srv = rust.server("67.161.116.223:28016")
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 71% 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
- 67.161.116.223:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:46 UTC
- hostname
- –
- first seen
- 1 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 · 150 on average | 104/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 153/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 45/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Population
What position does Corrosion Hour Development Test Server take in the server rankings?
Over the last seven days Corrosion Hour Development Test Server sits at #16,010 on player hours, in the top 71% of ranked servers.
What population does Corrosion Hour Development Test Server carry?
Corrosion Hour Development Test Server returns no live count at this refresh, having last been seen 25 days 9 hours ago.
Server facts
What Rust version does Corrosion Hour Development Test Server run?
Rust network protocol 2634 and build 166493 on Windows is what Corrosion Hour Development Test Server runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Corrosion Hour Development Test Server, and is it up?
Offline now for Corrosion Hour Development Test Server, last seen 25 days 9 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 1 October 2026.
Which location does Corrosion Hour Development Test Server run from?
No region is published by Corrosion Hour Development Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 67.161.116.223:28015.
Rules, settings, map
Which settings and rules does Corrosion Hour Development Test Server run?
No gather rate appears in the name: Corrosion Hour Development Test Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on Corrosion Hour Development Test Server?
The game generates its map: procedural, on Corrosion Hour Development Test Server.
Wipe schedule
When does Corrosion Hour Development Test Server wipe, and on what schedule?
A rhythm cannot be read from the wipes of Corrosion Hour Development Test Server on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 13 hours ago.
Tags and filters
Where does Corrosion Hour Development Test Server appear among Rust Data lists and filters?
On Rust Data, Corrosion Hour Development Test Server appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Corrosion Hour Development Test Server?
These tags are published by Corrosion Hour Development Test Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166493 (Build): Recorded game build: 166493; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
How to join
What is the way into Corrosion Hour Development Test Server?
Enter client.connect 67.161.116.223:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.