Rust Data

rustdata.spaceservers94.158.50.72:27017.ipynb

Run all rust-data · live

‹ All servers

Offline 94.158.50.72:28015 checked 12d ago

PVE NIKOV|TP|RAIDBASE|BOSS|EVENT

biweekly wipes moddedoxidepve

Connect

srv = rust.server("94.158.50.72:27017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,114 # top 70%
last wipe 23d ago # biweekly schedule
next wipe 4d 11h # Mon 2 Nov, 17:26 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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. 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
RankRank in region
15k10k15k20k5 Oct9 Oct12 Oct16 Oct19 Oct23 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Monday 2 November, 17:26 UTC, in 4d 11h. # Its biweekly schedule tag · low confidence

wipe-day peak2players, last three wipes

Coming wipes

inatkind
04d 11hMon 2 Nov, 17:26 UTCwipe
17d 12hThu 5 Nov, 19:00 UTCFW force wipe
218d 11hMon 16 Nov, 17:26 UTCwipe
332d 11hMon 30 Nov, 17:26 UTCwipe
435d 12hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 23 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 5 Oct, 17:26 UTC23d ago 2 NaN 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
94.158.50.72:28015
region
–
max players
50
group limit
8, the default
wipe schedule
biweekly
last wipe
5 Oct 2026, 18:08 UTC
hostname
–
first seen
5 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 252 on average188/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 241 on average81/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 105 on average62/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 59 on average52/200
4TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 50 on average19/100
5Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsidgroups of 8+ · biweekly · 48 on average27/250

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT rank?

Rank #15,114 on seven-day player hours for PVE NIKOV|TP|RAIDBASE|BOSS|EVENT, within the top 70% of all ranked servers.

How full does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT run?

Offline now for PVE NIKOV|TP|RAIDBASE|BOSS|EVENT, with the last sample 12 days 21 hours ago.

Server data

What Rust version does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT run?

Version Rust network protocol 2634 and build 167781 on Linux is reported by PVE NIKOV|TP|RAIDBASE|BOSS|EVENT. Joining needs the same protocol on your game; Steam handles the update.

How reliable is PVE NIKOV|TP|RAIDBASE|BOSS|EVENT, and is it online now?

The latest sample has PVE NIKOV|TP|RAIDBASE|BOSS|EVENT offline, with a last sighting 12 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 5 October 2026.

In which location is PVE NIKOV|TP|RAIDBASE|BOSS|EVENT hosted?

No region is published by PVE NIKOV|TP|RAIDBASE|BOSS|EVENT. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 94.158.50.72:28015 is its address.

Settings and map

What rules and settings are recorded for PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?

No gather rate appears in the name: PVE NIKOV|TP|RAIDBASE|BOSS|EVENT. The group limit sits at the default of 8 players. pve is the game mode here, and no combat between players. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?

The game generates its map: procedural, on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT.

Wipes and dates

When does PVE NIKOV|TP|RAIDBASE|BOSS|EVENT wipe, and on what schedule?

The tag sets the prediction: PVE NIKOV|TP|RAIDBASE|BOSS|EVENT has too few wipes on record to confirm its schedule. On Monday 2 November at 17:26 UTC the next wipe is due. The world it runs now was generated 23 days 11 hours ago. Its tags carry a wipe schedule of every two weeks.

On PVE NIKOV|TP|RAIDBASE|BOSS|EVENT, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 23 hours in.

Lists and tags

Which Rust Data filters and lists contain PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?

On Rust Data, PVE NIKOV|TP|RAIDBASE|BOSS|EVENT appears in these lists: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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.

Which meanings do the tags on PVE NIKOV|TP|RAIDBASE|BOSS|EVENT hold?

These tags are published by PVE NIKOV|TP|RAIDBASE|BOSS|EVENT and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to PVE NIKOV|TP|RAIDBASE|BOSS|EVENT?

The manual route: launch Rust, F1, then client.connect 94.158.50.72:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2634,^b,^p,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players Slot count: 50.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build Build number: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The cycle is fourteen days.

Gameplay

^p
PvE No player-versus-player combat; the danger comes from the world.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 32,693 players 11,617 servers online