Rust Data

rustdata.spaceservers208.52.153.33:28046.ipynb

Run all rust-data · live

‹ All servers

Online 208.52.153.33:28049 checked 10m ago

№[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events

monthly wipes vanillamoddedoxide

Connect

srv = rust.server("208.52.153.33:28046")
print(srv.connect_command)

Right now

srv.summary()
players now 3/60 # 5% full
7-day average 1 # peak 6
rank #3,674 # top 16%
last wipe 27d ago # monthly schedule
next wipe 7d 15h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
0123404:0013:0022:0007:0016:0002:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304004:0013:0022:0007:0016:0002: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 17 Sep. 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
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. # The force wipe · high confidence

wipe-day peak6players, last three wipes

Coming wipes

inatkind
07d 15hThu 5 Nov, 19:00 UTCFW force wipe
135d 15hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 6, 36 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 19:28 UTC FW27d ago 6 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

4000 · seed 1903718342
Map of №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events
map
Procedural Map
size
4000
seed
1903718342
Open on RustMaps

Server

srv.info()
address
208.52.153.33:28049
region
–
max players
60
group limit
8, the default
wipe schedule
monthly
last wipe
1 Oct 2026, 19:28 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Overrun-Z: PvE Chaos Zombies. Raids. Relentless Combat. The world didn’t end - it was overrun. Face endless hordes, raidable bases, and faction wars packed with loot and danger. Trigger Events: Skyfall Airdrops, Arctic Assaults, Iron Dock Raids. Raidable Bases: Easy → Nightmare, big risk, bigger reward. Dog Tag Economy: Trade tags for RP and upgrades. Daily RP Boosts: Mon/Wed x3 | Tue/Thu x2 | Nights x2

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

rust.similar(srv).head(6)
serverlike_thisplayers
0AQRUX RUST BUILD | CREATIVE | SANDBOXEU · groups of 8+ · monthly · 24 on average2/100
1Art of Rust - Official dedicated art servergroups of 20+ · monthly · 8 on average10/100
2RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGradeNA · groups of 100+ · monthly · 7 on average11/200
3[EU]Luuxens[PVE&RP]Town|Drugs|Quests|Tiers|Roles|RaidBases|FireEU · groups of 16+ · monthly · 6 on average4/50
4UTC | BUILDING | CREATIVE | BUILD | ПАЛЯНИЦЯ | EU | UAEU · groups of 8+ · monthly · 3 on average4/40
5[EU]FreeFields/Creative/Building/SandboxEU · groups of 8+ · monthly · 3 on average0/35

Quick answers

From the figures on this page.

Population

How does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events compare in the rankings?

Player hours over seven days put №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events at #3,674, in the top 16% of the ranked set.

How full does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events run?

The sample now reads 3 players for №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, out of 60 slots. Over the last seven days it averaged 1 players and peaked at 6. Averaged by hour over 48 hours, 01:00 UTC is the busiest, at 3 players.

About the server

What does performance look like on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

The 48-hour average is 30 server fps, with a low of 30. The entity count peaked at 110,762, covering buildings, deployables and the rest of the world. The memory field tops out at 3,800 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. Steam updates your game for you, but the protocol must match to join.

How reliable is №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, and is it up?

The current sample puts №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events online. Count back 14 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.

Which location does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events run from?

There is no region published for №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 208.52.153.33:28049.

Settings and map

Which rules apply on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, and what settings?

No gather rate appears in the name: №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. Eight players per group: that is the game's default, and it applies here. Recorded as build & creative, building in a sandbox, no gathering. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat status: VAC off.

Which map has №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events loaded?

Size 4,000, seed 1903718342: the procedural map on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

On what schedule does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events wipe?

A single wipe each month, the force wipe, is all №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 27 days 7 hours ago, and that is the one in play. A monthly wipe schedule is published in its tags.

What is wipe day on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events like?

Recent wipes averaged 6 players at their peak. Peak population on the latest wipe came 36 hours in.

Tags, lists

Which lists on Rust Data hold №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, and which filters?

The Rust Data lists that №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events fits are: Modded Rust servers, Servers with build or creative tags, Rust creative servers, listed, Rust roleplay servers and Rust servers named for the undead. Under these filters on the server list, it is listed: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Roleplay ^r, Creative ^c, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Which meanings do the tags on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events hold?

The game's server browser reads these tags from №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events: gmrust (Game mode): Rust survival in its standard form; mp60 (Max players): The server lists 60 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^r (Roleplay): A server built for roleplay; ^c (Creative): Build freely, with no gathering: sandbox mode; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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

What is the way to join №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

Enter client.connect 208.52.153.33:28049 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://d2s.tebex.io/.

Server tags · what each one means

srv.tags.decode()

Published as mp60,ptrak,$r?,v2635,^m,^v,^r,^c,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp60
Max players The server lists 60 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Gameplay

^r
Roleplay A server built for roleplay.
^c
Creative Build freely, with no gathering: sandbox mode.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^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 34,855 players 11,686 servers online