Offline 73.100.78.56:28017 checked 32d ago
Nuke Event Test Server
Connect
srv = rust.server("73.100.78.56:28018")
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, measured since 17 Sep. 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
Top 72% 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())
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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population data
How does Nuke Event Test Server compare in the rankings?
Player hours over seven days put Nuke Event Test Server at #16,789, in the top 72% of the ranked set.
How many players does Nuke Event Test Server hold at once?
Nuke Event Test Server returns no live count at this refresh, having last been seen 32 days 3 hours ago.
About the server
What is the Rust version on Nuke Event Test Server?
Rust network protocol 2633 and build 163794 on Linux is what Nuke Event Test Server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Nuke Event Test Server, and is it online now?
Offline now for Nuke Event Test Server, last seen 32 days 3 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 17 September 2026.
Which location does Nuke Event Test Server run from?
No region is published by Nuke Event Test Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 73.100.78.56:28017.
Settings and map
What rules and settings are recorded for Nuke Event Test Server?
No gather rate appears in the name: Nuke Event Test Server. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: 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. Anti-cheat status: VAC on.
What is the map on Nuke Event Test Server?
Nuke Event Test Server runs a procedural map of size 3,000 with seed 960991987, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.
Wipe data
When does Nuke Event Test Server wipe, and how often?
A rhythm cannot be read from the wipes of Nuke Event Test Server on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 41 days 19 hours ago, and that is the one in play.
Tags and filters
Which Rust Data filters and lists contain Nuke Event Test Server?
These Rust Data lists include Nuke Event Test Server: 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.
How should you read the server tags on Nuke Event Test Server?
Read by the game's server browser, the tags Nuke Event Test Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): The server runs build 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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
What is the way to join Nuke Event Test Server?
In Rust, F1 opens the console: type client.connect 73.100.78.56:28017. Launch Rust on this page does the same by opening the game through Steam and connecting.