Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO P SRV11,703online PAX41,069playing OCC3,025with players WIPED 3H98
MODModded traffic
Callsign

DDR7781=

DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS

Online 37.244.237.248:28015 checked 8m ago

biweekly wipes moddedoxidepve
Clearance · join
Players now 0/ 100 0% full
7-day average0peak 2
Rank#7,781top 35%
Last wipe6d agobiweekly schedule
Next wipe7d 17hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
0123402:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

Server performance

05010015020002:0011:0020:0005:0014:0000: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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k30 Sep6 Oct12 Oct17 Oct23 Oct29 Oct

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

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 7d 17h.

The force wipe · high confidence

usual gap4.6 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 1

Coming wipes

  1. 7d 17hThu 5 Nov, 19:00 UTCFW
  2. 12d 8hTue 10 Nov, 10:04 UTC
  3. 26d 8hTue 24 Nov, 10:04 UTC
  4. 35d 17hThu 3 Dec, 19:00 UTCFW
  5. 40d 8hTue 8 Dec, 10:04 UTC

The first 48 hours of its last wipes

Tue 13 OctThu 8 OctFri 2 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 10:04 UTC15d ago 1 – running 0
Thu 8 Oct, 20:35 UTC20d ago 2 halved by day 1 4.6 days 0
Fri 2 Oct, 12:26 UTC26d ago 2 held half 6.3 days 1
Thu 1 Oct, 17:35 UTC FW27d ago 2 – 0.8 days 1

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 BRT016NA · no group limit · biweekly · 249 on average [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo
    Players 309/2000
  2. 02MOD
    Callsign BRT016EU · no group limit · biweekly · 240 on average [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo
    Players 131/2000
  3. 03MOD
    Callsign CHR017NA · groups of 8+ · biweekly · 103 on average Chrayntopia ♡ ︎PvE | RP | PvP
    Players 178/200
  4. 04MOD
    Callsign PVE016EA · groups of 16+ · biweekly · 60 on average 【炮炮PVE启蒙】纯净|特色|突袭|技能
    Players 28/200
  5. 05MOD
    Callsign TRV010EU · groups of 30+ · biweekly · 51 on average TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10
    Players 11/100
  6. 06MOD
    Callsign EMP015groups of 8+ · biweekly · 49 on average Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid
    Players 53/250
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

On Rust Tracker, DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS sits in these lists: PvE servers, tracked live and Modded servers, tracked live. These filters surface it on the server list: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.

How should you read the tags on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

These tags are published by DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS for the game's server browser to read: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): A wipe every fortnight; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Times

What happens on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS on wipe day?

Recent wipes averaged a peak of 2 players. 1 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. The fall below half came by day 1 where it did not hold.

On what schedule does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS wipe?

The prediction for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS follows its tag, as too few wipes are on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. 6 days 7 hours since this world was made. Tags list a wipe schedule of every two weeks.

Location and Status

How reliable is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, and is it online now?

Tracking shows DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS online as of now. By its own uptime figure, the last restart was roughly 22 hours ago. Uptime stood at 99% for the last 7 full days, 167 of 168 hours online. The first sighting by Rust Tracker was 30 September 2026.

What Rust version is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS on?

Rust network protocol 2635 and build 168909 on Windows is what DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS runs. The same protocol is required to join, and Steam updates it for you.

What is performance like on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

Server fps held an average of 135 across the last 48 hours, never below 59. Maximum entities carried: 74,387, from buildings and deployables to everything else. Peak memory use: 3,078 MB. Players feel lag when fps drops and the entity count climbs.

What location is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS hosted in?

No region is published by DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 37.244.237.248:28015.

Player Count

What is the player count on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

Tracking DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS: 0 of 100 slots filled. Peak of 2 in the last seven days, average 0 players.

How does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS compare in the rankings?

Seven-day player hours put DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS at #7,781, within the top 35% of all ranked servers.

Settings

Which settings and rules are confirmed on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

No gather rate appears in DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS's name. The game's default applies: groups can have up to 8 players. It runs pve, fighting between players is off. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. VAC is on, Valve's anti-cheat.

Which map is confirmed for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

The map on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS is procedural, size 3,500, seed 1525560128, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

How do you get onto DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

To connect: start Rust, press F1, enter client.connect 37.244.237.248:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://deadrop-server.duckdns.org/.

Transponder codes

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2635,^b,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival mode for Rust.
mp100
Max players 100 slots on this server.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; listed 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.