Station XX-7779 · recording
DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS
Online 37.244.237.248:28015 checked 13m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 2
- Rank
- #7,779
- top 35%
- Last wipe
- 6d ago
- biweekly schedule
- Next wipe
- 7d 9h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 35% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 9h. The force wipe · high confidence
- usual gap
- 4.6 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 2players, last three wipes
- crowd held
- 50%else halves by day 1
Coming wipes
- 7d 9hThu 5 Nov, 19:00 UTCFW
- 12d 0hTue 10 Nov, 10:04 UTC
- 26d 0hTue 24 Nov, 10:04 UTC
- 35d 9hThu 3 Dec, 19:00 UTCFW
- 40d 0hTue 8 Dec, 10:04 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 13 Oct, 10:04 UTC15d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 8 Oct, 20:35 UTC20d ago | M0.3▲rising | 2 | halved by day 1 | 4.6 days | 0 | |
| Fri 2 Oct, 12:26 UTC26d ago | M0.0▲rising | 2 | held half | 6.3 days | 1 | |
| Thu 1 Oct, 17:35 UTC FW27d ago | M0.0▲rising | 2 | – | 0.8 days | 1 |
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 pageMap and rules
Which map is running on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?
Generated by the game, the map on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS is procedural, size 3,500 with seed 1525560128. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?
You will find no gather rate in the name of DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. At the game's default, groups can have up to 8 players. It plays in pve mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?
At this moment, DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS records 0 players across 100 slots. The seven-day average is 0 players, with a peak of 2.
How does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS rank against other Rust servers?
Over the last seven days, DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS recorded enough player hours to reach #7,779 worldwide, placing it in the top 35% of all ranked servers.
Operator and location
How reliably does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS stay online?
DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS is up at the moment. Its reported uptime points to a restart about 6 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 30 September 2026 is when Rust Server Trends first recorded it.
How well does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS perform under load?
The 48-hour average is 132 server fps; 58 is the lowest observed. The world held up to 74,823 entities at its peak, buildings and deployables included. Its highest memory use was 3,078 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS hosted?
No region is published by DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 37.244.237.248:28015.
Which Rust version is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS running?
Rust network protocol 2635 and build 168909 on Windows is what DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?
The recent wipes averaged a busiest count of 2 players. 1 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 50% of its recent wipes. It fell under half by day 1 in the wipes where it didn't hold.
On what timetable does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS run its wipes?
The prediction follows its tag, because too few of DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS's wipes are on record to confirm its schedule. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 6 days 15 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Server tags
What do the server tags on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS mean?
The game's server browser reads the tags DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS publishes: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 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): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^b (Biweekly): It wipes once a fortnight; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS appear?
You will find DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: 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.
Join the server
What steps get you onto DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?
Enter client.connect 37.244.237.248:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://deadrop-server.duckdns.org/.
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.