Online NA 72.73.28.150:28030 checked 12m ago
Nuclear US - Vanilla | BiWeekly
Connect
srv = rust.server("72.73.28.150:28032")
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 31% of all ranked servers, top 58% in NA. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 18h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 18h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 20d 17h | Thu 19 Nov, 17:52 UTC | wipe |
| 2 | 34d 18h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 41d 17h | Thu 10 Dec, 17:52 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 34 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 17:52 UTC6h ago | NaN | NaN | running | 0 |
| 1 | Thu 15 Oct, 17:53 UTC14d ago | 5 | NaN | NaN | 0 |
| 2 | Thu 1 Oct, 17:56 UTC FW28d ago | 1 | halved by day 6 | 14 days | 0 |
| 3 | Thu 17 Sep, 17:55 UTC42d ago | 2 | held half | 14 days | 0 |
# 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())
Operator · nucleargaming.io
rust.servers(operator="nucleargaming.io").sort_values("players")
| server | players | |
|---|---|---|
| 0 | Nuclear Cargo/Oil Trainer | 3/40 |
| 1 | Nuclear 3x | 0/50 |
| 2 | NuclearPremium - Vanilla | 0/40 |
4 servers publish a nucleargaming.io hostname.
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rustopia.gg - US Medium | NA · groups of 12+ · biweekly · 89 on average | 536/550 |
| 1 | Rusty Moose |US Biweekly| | NA · groups of 12+ · biweekly · 67 on average | 791/800 |
| 2 | Gringers Solo Only | Noob Friendly Oct 22 | NA · groups of 8+ · biweekly · 43 on average | 42/100 |
| 3 | Rustoria.co - US Medium Premium | NA · groups of 12+ · biweekly · 38 on average | 299/300 |
| 4 | Reddit.com/r/PlayRust - US Biweekly | NA · groups of 12+ · biweekly · 23 on average | 24/200 |
| 5 | Rustafied.com - US Medium - Large | NA · groups of 16+ · biweekly · 22 on average | 46/350 |
Quick answers
From the figures on this page.
Player counts
How does Nuclear US - Vanilla | BiWeekly compare in the rankings?
Player hours over the last seven days: #6,953 for Nuclear US - Vanilla | BiWeekly, #1,081 in North America, within the top 31% of the ranked set.
How full does Nuclear US - Vanilla | BiWeekly run?
The sample now reads 0 players for Nuclear US - Vanilla | BiWeekly, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 2. Peak hour in the last 48 hours: 19:00 UTC, mean 1 players.
Server data
What does performance look like on Nuclear US - Vanilla | BiWeekly?
Server fps over the last 48 hours averages 45; the floor is 41. The entity count peaked at 76,100, covering buildings, deployables and the rest of the world. A high of 3,439 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on Nuclear US - Vanilla | BiWeekly?
Rust network protocol 2635 and build 168909 on Linux is what Nuclear US - Vanilla | BiWeekly runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Nuclear US - Vanilla | BiWeekly, and is it up?
The current sample puts Nuclear US - Vanilla | BiWeekly online. Count back 5 hours from its reported uptime to get the last restart. 143 of 168 hours up over the last 7 full days, or 85%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does Nuclear US - Vanilla | BiWeekly run from?
The NA tag is what Nuclear US - Vanilla | BiWeekly uses to list itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 72.73.28.150:28030.
Settings and map
What rules and settings are recorded for Nuclear US - Vanilla | BiWeekly?
The name Nuclear US - Vanilla | BiWeekly carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. The plugin count is Carbon. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.
What is the map on Nuclear US - Vanilla | BiWeekly?
Nuclear US - Vanilla | BiWeekly runs a procedural map of size 3,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. Nuclear Map Generation is what the map name field says.
Wipe schedule
When does Nuclear US - Vanilla | BiWeekly wipe, and how often?
The wipe rhythm for Nuclear US - Vanilla | BiWeekly is every 3 weeks on Thursday at 17:52 UTC. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 6 hours ago. The tags list a two-weekly wipe cycle.
What is wipe day on Nuclear US - Vanilla | BiWeekly like?
The average peak over recent wipes is 3 players. 34 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 33% of the time. Otherwise the crowd fell below half by day 5.
Lists and tags
Which lists on Rust Data hold Nuclear US - Vanilla | BiWeekly, and which filters?
The Rust Data lists that Nuclear US - Vanilla | BiWeekly fits are: Rust community servers, unfiltered, North America Rust servers and Vanilla Rust servers. It appears under these filters on the server list: Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
Who operates Nuclear US - Vanilla | BiWeekly?
Nuclear US - Vanilla | BiWeekly and 3 other servers we track both publish a nucleargaming.io hostname, so the same operator most likely runs them.
Which meanings do the tags on Nuclear US - Vanilla | BiWeekly hold?
Read by the game's server browser, the tags Nuclear US - Vanilla | BiWeekly publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^y (Carbon): The plugin framework in use is Carbon; NA (North America): In the server browser it sits under North America. 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.
Connecting
What is the way to join Nuclear US - Vanilla | BiWeekly?
Enter client.connect 72.73.28.150:28030 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://nuclearrust.net is the website recorded for it.
