Rust Server TrendsSeismic network · station log
Recording Stations11,645 Players47,241 Active3,160 Wipes · 3 h103 48 h

Station XX-15920 · no signal

Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|

Offline 185.172.175.236:28085 checked 25d ago

moddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,920
top 70%
Last wipe
54d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15920 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 100 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep28 Sep1 Oct5 Oct9 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 155 on average
145/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 127 on average
125/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 115 on average
171/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average
86/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
4/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
38/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|?

The procedural map on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| is size 4,500 with seed 1610899211, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|?

You will find no gather rate in the name of Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| right now?

Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| is not responding at this moment and is offline, last seen 25 days 17 hours ago.

How does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| rank against other Rust servers?

On player hours for the past week, Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| sits at #15,920, which puts it inside the top 70% of every ranked server.

Server details

How reliably does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| stay online?

Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| is down at the moment; the last recorded contact was 25 days 17 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 15 September 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| hosted?

A region is not published by Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 185.172.175.236:28085.

Which Rust version is Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| running?

Rust network protocol 2633 and build 162929 on Windows is what Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

How often does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| wipe, and on which days?

The rhythm of Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 54 days 13 hours is how long the current world has been running.

Tags

What do the server tags on Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| mean?

These are the tags Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): Slots: 100; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs162929 (Build): It runs game build 162929; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| appear?

The Rust Server Trends lists that take in Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase| are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

What steps get you onto Nuclear Frontier v2.0 |PvE|Modded|Events|RaidableBase|?

You can connect by pressing F1 in Rust and typing client.connect 185.172.175.236:28085 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players Slots: 100.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs162929
Build It runs game build 162929.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.