StatusLive Servers online11,635 Players46,789 Populated3,178 Wiped · 3 h97 Interval5 min Date28 OCT 2026

DWG RG-S6937Server sheetchecked 8m ago

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

Online 37.244.237.248:28015 checked 8m ago

biweekly wipes moddedoxidepve
Connect
Players now 0/ 100 0% full
7-day average0peak 2
Rank#6,937top 31%
Last wipe5d agobiweekly schedule
Next wipe8d 10hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
00.250.50.75109:0018:0003:0013:0022:0007:00

Hourly average and peak, UTC.

Fig. 1Players on DEADROP PVE | IN-GAME MENU | RP | ZLVL |...
Fig. 2

Server performance

05010015020009:0018:0003:0013:0022:0007: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k30 Sep6 Oct11 Oct17 Oct22 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 8d 10h. 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. 8d 10hThu 5 Nov, 19:00 UTCFW
  2. 13d 1hTue 10 Nov, 10:04 UTC
  3. 27d 1hTue 24 Nov, 10:04 UTC
  4. 36d 10hThu 3 Dec, 19:00 UTCFW
  5. 41d 1hTue 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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 10:04 UTC14d ago 1 – running 0
Thu 8 Oct, 20:35 UTC19d ago 2 halved by day 1 4.6 days 0
Fri 2 Oct, 12:26 UTC25d ago 2 held half 6.3 days 1
Thu 1 Oct, 17:35 UTC FW26d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 246 on average
112 / 2000
02
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 236 on average
139 / 2000
03
Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 100 on average
40 / 200
04
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 59 on average
78 / 200
05
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 53 on average
30 / 100
06 13 / 250
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

Is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS online, and what uptime has been recorded?

DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS is up at this moment. The uptime it reports puts the last restart at about 5 hours ago. 168 of 168 hours up over the last 7 full days, which is 100% of the time. The first sighting of it by Rust Graphs was on 30 September 2026.

Is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS stable in the figures recorded?

129 server fps on average over the last 48 hours, and never under 31. Counted at its highest: 74,465 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,242 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

No region is published by DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 37.244.237.248:28015 is its address.

On which Rust version is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS running?

The platform is Windows and the version is Rust network protocol 2635 and build 168909 on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. To join, your game must be on the same protocol; Steam handles the update.

Counts

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

Current player count on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS: 0, of 100 slots. The seven-day mean is 0 players; the peak over the same period is 2. Averaged over the last 48 hours, the player count is highest at 18:00 UTC: 1 players.

In the rankings, which position does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS hold?

Within the top 31% of all ranked servers: DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS at #6,937 for player hours, seven days recorded.

Wipe times

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

The recent wipes averaged a busiest count of 2 players. 1 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 50% of its recent wipes. By day 1 the crowd had fallen below half on the wipes where it did not hold.

On DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, when do wipes occur?

The prediction follows its tag, because too few wipes of DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been in use since 5 days 14 hours ago. The tags state a wipe schedule at two-week intervals.

Map and rules

Which settings does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS run, and what rules?

The name of DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS records no gather rate. No limit is published beyond the default: 8 players per group. It runs the pve game mode, no fighting other players. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.

What is the map for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

Size 3,500 with seed 1525560128: that is the procedural map DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

On Rust Graphs, which lists and filters contain DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

These Rust Graphs lists include DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: 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.

On DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): 100 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): Every two weeks it wipes; ^p (PvE): Player fights are off; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded are the tags DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Joining the server

What is the way to connect to DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

Connect with client.connect 37.244.237.248:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://deadrop-server.duckdns.org/.

NotesAnswered from the figures
Key

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, as Rust plays.
mp100
Max players 100 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Gameplay

^p
PvE Player fights are off; the world supplies the danger.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded