Skip to the page
Network live 11,696 servers online 65,102 players aboard 116 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Online 37.244.237.248:28015 checked 8m ago

biweekly wipes moddedoxidepve
Tracking number · connect
Launch Rust and join Website
Wipe progress · wiped 5d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Thu 5 Nov, 19:00 UK Thu 5 Nov, 19:00 UTC FW in 8d 7h · high confidence
0/ 100 players now 0% full
07-day averagepeak 2
#6,931ranktop 31%
5d agolast wipebiweekly schedule
8d 7hnext wipeThu 5 Nov, 19:00 UTC FW
Delivery history

Players, performance and rank

Players

AveragePeak
00.250.50.75112:0021:0006:0016:0001:0010:00

Hourly average and peak, UTC.

Server performance

05010015020012:0021:0006:0016:0001:0010: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 Oct11 Oct17 Oct22 Oct28 Oct

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

Wipe schedule

from its schedule tag
Next delivery expected

Next wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 8d 7h.

The force wipe · high confidence
4.6 daysusual gapbetween real wipes
33%on rhythmof its recent wipes
2wipe-day peakplayers, last three wipes
50%crowd heldelse halves by day 1

Coming wipes

  1. 8d 7hThu 5 Nov, 19:00 UTC19:00 UKFW
  2. 12d 22hTue 10 Nov, 10:04 UTC10:04 UK
  3. 26d 22hTue 24 Nov, 10:04 UTC10:04 UK
  4. 36d 7hThu 3 Dec, 19:00 UTC19:00 UKFW
  5. 40d 22hTue 8 Dec, 10:04 UTC10:04 UK

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

every wipe as a delivery, newest first
  1. Thu 5 Nov, 19:00 UTC FW19:00 UK · in 8d 7h
    Next wipe expected · the force wipe
  2. Tue 13 Oct, 10:04 UTC 11:04 UK · 15d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  3. Thu 8 Oct, 20:35 UTC 21:35 UK · 19d ago
    Wipe delivered
    Peak
    2
    Crowd
    halved by day 1
    Lasted
    4.6 days
    Players before
    0
  4. Fri 2 Oct, 12:26 UTC 13:26 UK · 25d ago
    Wipe delivered
    Peak
    2
    Crowd
    held half
    Lasted
    6.3 days
    Players before
    1
  5. Thu 1 Oct, 17:35 UTC FW 18:35 UK · 26d ago
    Force wipe delivered
    Peak
    2
    Crowd
    –
    Lasted
    0.8 days
    Players before
    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.

Similar parcels

Similar servers

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

  1. [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 246 on average 67 / 2000
  2. [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 236 on average 189 / 2000
  3. Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 100 on average 28 / 200
  4. 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能EA · groups of 16+ · biweekly · 58 on average 107 / 200
  5. TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 52 on average 46 / 100
  6. Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsidgroups of 8+ · biweekly · 51 on average 14 / 250
Help desk

Quick answers

From the figures on this page.

Population

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

In the top 31% of all ranked servers sits DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, at #6,931 on hours played over seven days.

Is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS busy at the moment?

The current count is 0 players on 100 slots for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. Averaged over the past week: 0 players, peaking at 2. The busiest hour over the last 48 hours was 18:00 UTC, averaging 1 players.

Rules and settings

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

Size 3,500 and seed 1525560128 define the procedural map DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS runs, generated by the game. Identical size and seed give an identical map: view it on RustMaps from this page.

What settings and rules should you know for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

You will not find a gather rate in the name of DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. 8 players is the group limit, since the game's default applies. It runs pve, other players cannot be fought. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Oxide supplies the plugins. VAC, Valve's anti-cheat, is switched on.

About the server

What is the location of DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?

No region is published by DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. You will find it at 37.244.237.248:28015.

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

The 48-hour average for server fps stands at 127, never dipping below 31. Buildings, deployables and all the rest of the world pushed its entity count as high as 74,465. Memory use peaked at 3,242 MB. Players feel a rising entity count and low fps as lag.

Is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS up, and how good is its uptime?

Right now, DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS is online. Its reported uptime suggests a restart roughly 8 hours ago. 100% is the uptime for the last 7 full days, up for 168 of 168 hours. 30 September 2026 is when Rust Wipe Tracker first recorded it.

On what Rust version does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS operate?

The version on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS is Rust network protocol 2635 and build 168909, running on Windows. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe schedule

How does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS handle its wipe days?

The average busiest point of its recent wipes was 2 players. 1 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held until the next wipe in 50% of recent wipes. In the other cases it sank under half by day 1.

How often does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS wipe, and at what times?

Since the record holds too few of DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS's wipes to confirm the schedule, the prediction goes by its tag. On Thursday 5 November at 19:00 UTC comes its next wipe, the force wipe that every Rust server shares. You are playing a world created 5 days 17 hours. In its tags it posts a wipe every two weeks.

Server tags

On Rust Wipe Tracker, which lists and filters is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS part of?

You will find DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS on the following Rust Wipe Tracker lists: Modded Rust servers and Best Rust PvE servers. You will find it under these filters 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?

gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slot count: 100; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): No region code is set; ^b (Biweekly): A wipe comes every fortnight; ^p (PvE): There's no player combat; the world itself is the threat; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded are the tags DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

Getting started

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

Enter client.connect 37.244.237.248:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you. Its website can be found at https://deadrop-server.duckdns.org/.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players Slot count: 100.
ts8
Group limit The game default caps teams at 8.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly A wipe comes every fortnight.

Gameplay

^p
PvE There's no player combat; the world itself is the threat.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded Plugins or settings alter the game, so it's 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.