Rust Data

rustdata.spaceservers203.16.163.8:27388.ipynb

Run all rust-data · live

‹ All servers

Online 203.16.163.8:27387 checked 8m ago

Drift Staging

moddedoxide

Connect

srv = rust.server("203.16.163.8:27388")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak 1
rank #14,792 # top 66%
last wipe 15d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123420:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040020:0005:0014:0023:0008:0017:00

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 4 Oct. 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
15k10k15k20k4 Oct9 Oct14 Oct19 Oct24 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.9 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Wed 14 OctTue 13 OctMon 12 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 14 Oct, 15:15 UTC15d ago 2 NaN running 0
1 Tue 13 Oct, 17:17 UTC16d ago 5 NaN 0.9 days 0
2 Mon 12 Oct, 20:37 UTC16d ago 5 NaN 0.9 days 0
3 Mon 5 Oct, 14:21 UTC24d ago 2 halved by day 1 7.3 days 0
4 Sun 4 Oct, 15:18 UTC25d ago 2 NaN 1 days 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

3500 · seed 50000
Map of Drift Staging
map
Custom Map
size
3500
seed
50000

Server

srv.info()
address
203.16.163.8:27387
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
14 Oct 2026, 16:27 UTC
hostname
–
first seen
4 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 151 on average113/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average133/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average196/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average73/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 90 on average211/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average348/350

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Drift Staging rank?

Rank #14,792 on seven-day player hours for Drift Staging, within the top 66% of all ranked servers.

What population does Drift Staging carry?

Current row: 0 players on Drift Staging, against 40 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

How smoothly does Drift Staging run?

Averaged over 48 hours: 170 server fps, never under 108. The entity count peaked at 24,268, covering buildings, deployables and the rest of the world. Memory peaked at 3,701 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does Drift Staging run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by Drift Staging. Joining needs the same protocol on your game; Steam handles the update.

Is Drift Staging up, and what does its uptime show?

Online is the state at the latest refresh for Drift Staging. Count back 2 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 4 October 2026.

Where does Drift Staging sit?

For Drift Staging, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 203.16.163.8:27387 is its address.

Map and rules

What rules and settings are recorded for Drift Staging?

No gather rate appears in the name: Drift Staging. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.

What is the map on Drift Staging?

Drift Staging runs a procedural map of size 3,500 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.

Wipe schedule

On what schedule does Drift Staging wipe?

No next wipe can be predicted for Drift Staging, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 15 days 2 hours ago.

What is wipe day on Drift Staging like?

The average peak over recent wipes is 4 players. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 1.

Lists and tags

Where does Drift Staging appear among Rust Data lists and filters?

On Rust Data, Drift Staging appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on Drift Staging?

The game's server browser reads these tags from Drift Staging: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way into Drift Staging?

The manual route: launch Rust, F1, then client.connect 203.16.163.8:27387. 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 mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players 40 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins 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.

Rust Data 103,453 players 11,891 servers online