RUST METRICSFlight deck · live data
Data live Servers11,737 Players72,806 Populated3,664 Fresh wipes 3 h128 Scan5 min
‹ All servers208.52.153.33:28049
Online Full Queue Fresh wipe Wipe due No query

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

Online 208.52.153.33:28049 checked 10m ago

monthly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Wed 11:00 UTC
0 15 30 45 60 PAX 1 /60

Players now

2% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 30 SERVER FPS

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 107,363 ×1000

Entities

48 h range 103,978–110,762 · memory 3,399 MB
1239 ET SINCE RESTART 23:19

Uptime

23 h 19 min since its last restart, at the last reading
7-day average1peak 6
Rank#3,772top 17%
Last wipe26d agomonthly schedule
Next wipe8d 5hThu 5 Nov, 19:00 UTC FW
Memory3,399MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5214:0023:0008:0017:0002:0011:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304014:0023:0008:0017:0002:0011: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.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

force wipes only

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

wipe-day peak6players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 5hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 5hFW

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 19:28 UTC FW26d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

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

At their busiest, its recent wipes drew 6 players on average. Peak crowd on the latest wipe: 36 hours in.

How often does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events wipe, and when?

Once a month №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events wipes, with the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 26 days 17 hours ago. A monthly wipe schedule is published in its tags.

Tag meanings

Which tags does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp60 (Max players): 60 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^r (Roleplay): Check: mode. Roleplay; ^c (Creative): Check: mode. Creative, where you build what you like and gather nothing; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

Rust Metrics lists featuring №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events: Modded Rust servers, checked live, Build and creative servers, Rust creative servers, Rust roleplay servers and Rust servers: zombie readings. These filters bring it up 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.

Occupancy

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

Ranking for №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events: #3,772 on seven-day player hours, top 17% of all ranked servers.

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

Current headcount on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events: 1 players, 60 slots available. Check: players over seven days. Average 1, peak 6. Check: 48-hour peak. 03:00 UTC, 2 players on average.

Operator and location

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

Reading: location. №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 208.52.153.33:28049.

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

Reading: №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

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

Check: fps. Average 30 server fps over the last 48 hours, low of 30. Within range. Reading: 110,762 entities at the highest. That covers buildings, deployables and everything else. Reading: 3,800 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, and is it online?

Check: connection. №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events is online at this moment. Reading: uptime. About 23 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

How is №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events configured, and what rules are in force?

Check: gather rate. The name №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events does not state one. 8 players per group, the default value. The mode is build & creative. Note the following: a build sandbox with no gathering. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Anti-cheat reading: VAC off, Valve's system.

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

From seed 1903718342, the game generates the procedural map on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. Its size is 4,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

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

Press F1 in Rust and enter client.connect 208.52.153.33:28049. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://d2s.tebex.io/ is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp60
Max players 60 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Gameplay

^r
Roleplay Check: mode. Roleplay.
^c
Creative Check: mode. Creative, where you build what you like and gather nothing.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.