Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO Y SRV11,598online PAX34,006playing OCC2,835with players WIPED 3H67
MODModded traffic
Callsign

OVR3846=

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

Online 208.52.153.33:28049 checked 13m ago

monthly wipes vanillamoddedoxide
Clearance · join
Players now 2/ 60 3% full
7-day average1peak 6
Rank#3,846top 17%
Last wipe26d agomonthly schedule
Next wipe8d 14hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
00.511.5205:0014:0023:0009:0018:0003:00

Hourly average and peak, UTC.

Server performance

01020304005:0014:0023:0009:0018:0003: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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Flight plan

Wipe schedule

force wipes only
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 8d 14h.

The force wipe · high confidence

wipe-day peak6players, last three wipes

Coming wipes

  1. 8d 14hThu 5 Nov, 19:00 UTCFW
  2. 36d 14hThu 3 Dec, 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 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign AQR511EU · groups of 8+ · monthly · 23 on average AQRUX RUST BUILD | CREATIVE | SANDBOX
    Players 10/100
  2. 02MOD
    Callsign ART015groups of 20+ · monthly · 8 on average Art of Rust - Official dedicated art server
    Players 6/100
  3. 03MOD
    Callsign RGB016NA · groups of 100+ · monthly · 7 on average RGB Creative Build | US Sandbox | Save/Load, Symmetry, BGrade
    Players 6/200
  4. 04MOD
    Callsign LXN015EU · groups of 16+ · monthly · 6 on average [EU]Luuxens[PVE&RP]Town|Drugs|Quests|Tiers|Roles|RaidBases|Fire
    Players 0/50
  5. 05MOD
    Callsign UTC010EU · groups of 8+ · monthly · 3 on average UTC | BUILDING | CREATIVE | BUILD | ПАЛЯНИЦЯ | EU | UA
    Players 0/40
  6. 06MOD
    Callsign FRF001EU · groups of 8+ · monthly · 3 on average [EU]FreeFields/Creative/Building/Sandbox
    Players 1/35
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

Modded servers, tracked live, Build, creative and sandbox servers, Rust creative servers, tracked live, Roleplay Rust servers, tracked live and Zombie servers, on radar — the Rust Tracker lists that include №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. These filters surface it 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.

What do the tags mean that №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events is listed under?

The game's server browser reads these tags from №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events: gmrust (Game mode): Rust survival, standard mode; mp60 (Max players): 60 slots on this server; ts8 (Group limit): Default team size: 8; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^m (Monthly): Monthly wipe, on Facepunch's force wipe; ^v (Vanilla): Facepunch's game unaltered: rates, kits and rules unchanged; ^r (Roleplay): Server type: roleplay; ^c (Creative): Build freely — sandbox building with no gathering; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

What should you expect on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events when wipe day lands?

Recent wipes averaged a peak of 6 players. 36 hours after the latest wipe, the crowd peaked.

Which wipe times are confirmed for №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

One wipe a month for №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events: the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Its world went live 26 days 9 hours. Tags list a monthly wipe schedule.

Location and Status

Is №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events up, and how does its uptime hold?

Tracking shows №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events online as of now. About 15 hours ago it restarted last, based on reported uptime. 100% uptime over the last 7 full days, with 168 of 168 hours up. First contact for Rust Tracker: 13 September 2026.

Which Rust build 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. The same protocol is required to join, and Steam updates it for you.

Is №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events holding performance?

For the last 48 hours it averaged 30 server fps; the floor was 30. Peak entity count: 110,762, covering buildings, deployables and all else in the world. It drew as much as 3,521 MB of memory. A climbing entity count and low fps are what register as lag for players.

Which location is №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events in?

Region: none published by №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 208.52.153.33:28049.

Population

How many players are on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events right now?

Slots 60; players on board 2: that is №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events now. Seven-day average 1 players; peak 6. Peak traffic in the last 48 hours came at 03:00 UTC, averaging 2 players.

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

On player hours over seven days, №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events ranks #3,846, inside the top 17% of all ranked servers.

Map and Rules

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

Nothing in №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events's name states a gather rate. 8 players per group is the game's default, and the cap holds. build & creative is the game mode, building in a sandbox, no gathering. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Oxide. It uses the word vanilla for itself: facepunch's game unaltered: rates, kits and rules unchanged. VAC is off, Valve's anti-cheat.

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

A procedural map of size 4,000 runs on №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events, generated by the game from seed 1903718342. Same size, same seed, same map. RustMaps shows it, linked from this page.

Connect

Which steps join №[1] D2S Overrun-Z PvE 1000 Zombies Raidable Bases Events?

Open the console in Rust with F1 after starting the game, then type client.connect 208.52.153.33:28049. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://d2s.tebex.io/.

Transponder codes

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 Rust survival, standard mode.
mp60
Max players 60 slots on this server.
ts8
Group limit Default team size: 8.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^m
Monthly Monthly wipe, on Facepunch's force wipe.

Difficulty

^v
Vanilla Facepunch's game unaltered: rates, kits and rules unchanged.

Gameplay

^r
Roleplay Server type: roleplay.
^c
Creative Build freely — sandbox building with no gathering.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Under Modded: the game is changed by plugins or settings.

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.