Skip to the page
RUST ANALYTICS
LIVE84,984PLY11,724SRV
QUOTE 208.52.153.33:28049 Online checked 10m ago

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

monthly wipes vanillamoddedoxide
Players · last
0/ 60
+024h
0% full
Day range 0 4
7-day avg 1 peak 6
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
0/ 60
0% full
Change · 24h
+0
no reading a day ago
7-day average
1
peak 6
Rank
#3,045
top 14%
Rank · 7d ago
#2,848
197 places down
Last wipe
12d ago
monthly schedule
Next wipe
22d 0h
Thu 5 Nov, 19:00 UTC FW
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
195
player hours, last seven days
Map
4000
Procedural Map · seed 1903718342
First seen
13 Sep 2026
no hostname published

Players

AveragePeak
0123419:0000:0004:0009:0012:0017:00

Hourly average and peak, UTC. Busiest hour of the two days: 4 players.

Server performance

01020304019:0000:0004:0009:0012: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

force wipes only
Next wipeThursday 5 November, 19:00 UTCin 22d 0h

The force wipe · high confidence

wipe-day peak
6
players, last three wipes

Coming wipes

  1. 22d 0hThu 5 Nov, 19:00 UTCFW

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
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 19:28 UTC FW12d ago 6 – 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

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1AQRUX RUST BUILD | CREATIVE | SANDBOXEU · groups of 8+ · monthly · 26 on average52/100+8+19.1%
2Art of Rust - Official dedicated art servergroups of 20+ · monthly · 10 on average12/100−1−5.9%
3[EU]Luuxens[PVE&RP]Town|Drugs|Quests|Tiers|Roles|RaidBases|FireEU · groups of 16+ · monthly · 8 on average7/50−2−20.0%
4UTC | BUILDING | CREATIVE | BUILD | ПАЛЯНИЦЯ | EU | UAEU · groups of 8+ · monthly · 4 on average12/40+3+27.4%
5№[4] D2S WarZone PvE 1000 Zombies Raidable Basesgroups of 8+ · monthly · 3 on average3/40+3
6RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGradeNA · groups of 100+ · monthly · 3 on average9/200+5+116.0%

Quick answers

from the figures on this page

Rules & Settings

What settings and rules are in place on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

The name of №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events carries no gather rate. Up to 8 players per group, which is the game's default. It runs build & creative, no gathering: sandbox building only. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are running. Its self-description is vanilla: facepunch's build, untouched: no rate changes, no kits, no rule changes. VAC, Valve's anti-cheat, is disabled.

What is the current map on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

A procedural map of size 4,000 with seed 1903718342 runs on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, created by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Population

What is the rank of №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

For the last seven days, №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events holds rank #3,045 on player hours, in the top 14% of all ranked servers.

What is the population on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

0 of 60 slots on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events are filled right now. The mean over the last seven days is 1 players, reaching 6 at its highest. At 01:00 UTC in the last 48 hours, it averaged 3 players, the busiest hour.

Wipe Cycle

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

An average of 6 players marked the busiest point of its recent wipes. 36 hours after the latest wipe, the crowd reached its peak.

When does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events schedule its wipes?

The only wipe at №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events is the monthly force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes at that time. This world has been running for 12 days 23 hours. A monthly wipe schedule is published in its tags.

Server Overview

What is the server location for №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

There is no region published for №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 208.52.153.33:28049 is its address.

How is the performance on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

Average server fps for the last 48 hours is 30; the floor was 30. At its peak it held 103,588 entities: buildings, deployables and the rest of the world. Up to 3,336 MB of memory was used. Low fps and growing entities are the source of felt lag.

№[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events runs which version of Rust?

The build is Rust network protocol 2634 and build 167781 on Linux, running on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. The protocol has to match for you to join, and Steam applies that update.

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

Online at this moment: №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. 5 hours ago is when it last restarted, judging by the uptime it reports. 7 full days have passed with 93% uptime, 156 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.

Tags and Rankings

How should you interpret the tags on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp60 (Max players): It holds 60 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^m (Monthly): A single wipe each month, alongside Facepunch's force wipe; ^v (Vanilla): Facepunch's build, untouched: no rate changes, no kits, no rule changes; ^r (Roleplay): Its format is roleplay; ^c (Creative): Sandbox rules: nothing to gather, and the build is yours; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.

Where does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events show up in Rust Analytics lists and filters?

On Rust Analytics, №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events matches these lists: Modded Rust servers, Rust build and creative servers, Rust creative servers, Rust roleplay servers and Rust zombie servers. It appears under these filters on the server list: 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; Last wipe: In the last 2 weeks.

Joining the Server

What steps do I take to join №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

The console route: start Rust, press F1, enter client.connect 208.52.153.33:28049. The page's Launch Rust button opens Rust through Steam and connects you instead. For more information, go to https://d2s.tebex.io/.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp60
Max players It holds 60 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2634
Protocol To join, your game needs protocol 2634.
cs167781
Build Game build: 167781.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly A single wipe each month, alongside Facepunch's force wipe.

Difficulty

^v
Vanilla Facepunch's build, untouched: no rate changes, no kits, no rule changes.

Gameplay

^r
Roleplay Its format is roleplay.
^c
Creative Sandbox rules: nothing to gather, and the build is yours.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

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.