Working its way up from the back of the class: #15,920 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 619 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|?
Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 185.172.175.236:28085.
How reliable is Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|, and is it up?
The server is down: Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| is offline now, with the last sighting 26 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 15 September 2026.
On what Rust version does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| sit?
Rust network protocol 2633 and build 162929 on Windows is what Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| reset?
There are too few wipes on record for Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 55 days 13 hours have passed since this world was made.
Player numbers
What position does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| hold in the rankings?
Over the last seven days, Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| has #15,920 for player hours, in the top 70% of all ranked servers.
Is Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| a busy server?
It has been 26 days 17 hours since Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| was last seen, and it is offline right now.
Lists and filters
What do Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|'s tags stand for?
You'll see Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): This runs on build 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|?
The name of Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|?
The game generates the procedural map on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| at size 4,500 with seed 1610899211. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|?
To connect, start Rust, press F1, and type client.connect 185.172.175.236:28085. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).