Station XX-3780 · recording
№[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events
Online 208.52.153.33:28049 checked 9m ago
- Players now
- 0/ 60
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 6
- Rank
- #3,780
- top 17%
- Last wipe
- 26d ago
- monthly schedule
- Next wipe
- 8d 7h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 60 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +2into Wed 01:00 UTC
- Peak · 48 h
- 2most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 17% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 8d 7h. The force wipe · high confidence
- wipe-day peak
- 6players, last three wipes
Coming wipes
- 8d 7hThu 5 Nov, 19:00 UTCFW
- 36d 7hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 6, 36 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 19:28 UTC FW26d ago | M0.8▲rising | 6 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?
Generated by the game, the map on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events is procedural, size 4,000 with seed 1903718342. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?
You will find no gather rate in the name of №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. The group limit is 8 players, the game's default. build & creative is the game mode, no gathering, only sandbox building. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. By its own description it is vanilla: unchanged from Facepunch's release: no altered rates, kits or rules. The server has VAC off, Valve's anti-cheat.
Population
What is the current population on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?
A reading taken now shows 0 players on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, which has 60 slots. The seven-day average is 1 players, with a peak of 6. Averaged over the last 48 hours, the busiest hour was 03:00 UTC at 2 players.
How does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events rank against other Rust servers?
The last seven days of player hours place №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events at #3,780, in the top 17% of all ranked servers.
Operator and location
How reliably does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events stay online?
№[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events is up at the moment. Its reported uptime points to a restart about 22 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. 13 September 2026 is when Rust Server Trends first recorded it.
Does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events hold a steady tick rate?
Across the last 48 hours it averaged 30 server fps, with a floor of 30. Buildings, deployables and all the rest of the world's entities brought it to a high of 110,762. Its highest memory use was 3,800 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events run from?
No region is published by №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 208.52.153.33:28049 is the address it uses.
Which Rust version is №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events running?
Rust network protocol 2635 and build 168909 on Linux is what №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?
6 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 36 hours after the wipe.
On what timetable does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events run its wipes?
The force wipe is the only wipe №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events takes, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 26 days 16 hours. A monthly wipe schedule is published in its tags.
Tags
What do the server tags on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events mean?
The game's server browser reads the tags №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events publishes: gmrust (Game mode): Survival in standard Rust; mp60 (Max players): The server has 60 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^r (Roleplay): A server for roleplay; ^c (Creative): Build freely in sandbox mode, with no gathering; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events appear?
The Rust Server Trends lists that take in №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events are: Modded Rust servers, tracked live, Rust build and creative servers, live, Rust creative servers, Rust roleplay server trends and Rust zombie servers, by recorded population. On the server list, the filters it matches are: 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.
Join the server
What steps get you onto №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?
You can connect by pressing F1 in Rust and typing client.connect 208.52.153.33:28049 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://d2s.tebex.io/ is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.