On the class lists: D (54), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 4
Rank#7,587top 34%
Last wipe22d agobiweekly schedule
Next wipe5d 15hMon 2 Nov, 18:08 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
66/ 100
C+
Working its way up from the back of the class: #7,587 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 149 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
53/ 100
D
Moving up: up 423 places this week.
A fair term, with more to come.
Strongest in performance (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 16 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 34% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Monday 2 November, 18:08 UTC, in 5d 15h.
Its biweekly schedule tag · low confidence
Coming wipes
5d 15hMon 2 Nov, 18:08 UTC
8d 15hThu 5 Nov, 19:00 UTCFW
19d 15hMon 16 Nov, 18:08 UTC
33d 15hMon 30 Nov, 18:08 UTC
36d 15hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 5 Oct, 18:08 UTC22d ago
–
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?
No region is published for PVE NIKOV|TP|RAIDBASE|BOSS|EVENT. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 94.158.50.72:28015 is the address to use.
Is PVE NIKOV|TP|RAIDBASE|BOSS|EVENT up, and how steady is its uptime?
Right now, PVE NIKOV|TP|RAIDBASE|BOSS|EVENT is online. The uptime it reports puts the last restart at about 41 hours ago. It was up 98% of the time over the last 7 full days, 164 of 168 hours. On 4 October 2026, Rust Server Score saw it for the first time.
How well does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT run?
It never fell below 89 server fps in the last 48 hours, averaging 149. Buildings, deployables and everything else in the world added up to as many as 87,355 entities. Up to 2,957 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is PVE NIKOV|TP|RAIDBASE|BOSS|EVENT on?
Rust network protocol 2635 and build 168909 on Linux is what PVE NIKOV|TP|RAIDBASE|BOSS|EVENT runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT wipe its map?
The prediction follows its tag, because too few of PVE NIKOV|TP|RAIDBASE|BOSS|EVENT's wipes are on record to confirm the schedule. It is due to wipe next on Monday 2 November at 18:08 UTC. 22 days 8 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
Player count
What position does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT hold in the rankings?
Over the last seven days, PVE NIKOV|TP|RAIDBASE|BOSS|EVENT has #7,587 for player hours, in the top 34% of all ranked servers.
Is PVE NIKOV|TP|RAIDBASE|BOSS|EVENT a busy server?
PVE NIKOV|TP|RAIDBASE|BOSS|EVENT is showing 0 players right now, with 50 slots in total. The seven-day average is 0 players, with a peak of 4. Over the last 48 hours, the peak hour was 05:00 UTC, averaging 0 players.
Tags and filters
What do PVE NIKOV|TP|RAIDBASE|BOSS|EVENT's tags stand for?
You'll see PVE NIKOV|TP|RAIDBASE|BOSS|EVENT tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT appear in the Rust Server Score lists and filters?
These Rust Server Score lists count PVE NIKOV|TP|RAIDBASE|BOSS|EVENT among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: 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.
Server rules
Which rules does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT enforce, and what are its settings?
You will find no gather rate in the name of PVE NIKOV|TP|RAIDBASE|BOSS|EVENT. The default of 8 players applies as the group cap. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
PVE NIKOV|TP|RAIDBASE|BOSS|EVENT runs which map?
A procedural map of size 3,700 and seed 1034224783, generated by the game, is what PVE NIKOV|TP|RAIDBASE|BOSS|EVENT runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?
Enter client.connect 94.158.50.72:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^b,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).