Station XX-15114 · no signal
PVE NIKOV|TP|RAIDBASE|BOSS|EVENT
Offline 94.158.50.72:28015 checked 12d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,114
- top 70%
- Last wipe
- 23d ago
- biweekly schedule
- Next wipe
- 4d 22h
- Mon 2 Nov, 17:26 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Monday 2 November, 17:26 UTC, in 4d 22h. Its biweekly schedule tag · low confidence
- wipe-day peak
- 2players, last three wipes
Coming wipes
- 4d 22hMon 2 Nov, 17:26 UTC
- 7d 23hThu 5 Nov, 19:00 UTCFW
- 18d 22hMon 16 Nov, 17:26 UTC
- 32d 22hMon 30 Nov, 17:26 UTC
- 35d 23hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 23 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 5 Oct, 17:26 UTC23d ago | M0.3▲rising | 2 | – | running | 0 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?
The map on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT is procedural, produced by the game.
Which settings and rules apply on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?
The name of PVE NIKOV|TP|RAIDBASE|BOSS|EVENT gives no gather rate. The group limit is 8 players, the game's default. pve is the game mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT right now?
No players are recorded on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT at this moment; it is offline, and the last sighting was 12 days 10 hours ago.
How does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT rank against other Rust servers?
The last seven days of player hours place PVE NIKOV|TP|RAIDBASE|BOSS|EVENT at #15,114, in the top 70% of all ranked servers.
Server details
How reliably does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT stay online?
PVE NIKOV|TP|RAIDBASE|BOSS|EVENT is down at the moment; the last recorded contact was 12 days 10 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 5 October 2026.
Where in the world is PVE NIKOV|TP|RAIDBASE|BOSS|EVENT hosted?
No region is published by PVE NIKOV|TP|RAIDBASE|BOSS|EVENT. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 94.158.50.72:28015.
What build of Rust does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT use?
PVE NIKOV|TP|RAIDBASE|BOSS|EVENT is running Rust network protocol 2634 and build 167781 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?
On average, the busiest point of its recent wipes drew 2 players. 23 hours after the latest wipe, the crowd peaked.
On what timetable does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT run its wipes?
The prediction follows its tag, because too few of PVE NIKOV|TP|RAIDBASE|BOSS|EVENT's wipes are on record to confirm its schedule. The date of its next wipe is Monday 2 November at 17:26 UTC. The present world dates from 23 days 1 hours. Every two weeks it wipes, according to the schedule in its tags.
Lists and tags
What do the server tags on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT mean?
The game's server browser reads the tags PVE NIKOV|TP|RAIDBASE|BOSS|EVENT publishes: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): A wipe comes every second week; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT appear?
The Rust Server Trends lists that take in PVE NIKOV|TP|RAIDBASE|BOSS|EVENT are: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Join the server
What steps get you onto PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?
You can connect by pressing F1 in Rust and typing client.connect 94.158.50.72:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
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.