Online 37.244.237.248:28015 checked 14m ago
DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS
Connect
srv = rust.server("37.244.237.248:28017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 35% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 11d 23h | Tue 10 Nov, 10:04 UTC | wipe |
| 2 | 25d 23h | Tue 24 Nov, 10:04 UTC | wipe |
| 3 | 35d 8h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 39d 23h | Tue 8 Dec, 10:04 UTC | wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 13 Oct, 10:04 UTC16d ago | 1 | NaN | running | 0 |
| 1 | Thu 8 Oct, 20:35 UTC20d ago | 2 | halved by day 1 | 4.6 days | 0 |
| 2 | Fri 2 Oct, 12:26 UTC26d ago | 2 | held half | 6.3 days | 1 |
| 3 | Thu 1 Oct, 17:35 UTC FW27d ago | 2 | NaN | 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.
display(srv.map, srv.info())Map
3500 · seed 1525560128
- map
- Procedural Map
- size
- 3500
- seed
- 1525560128
Server
srv.info()- address
- 37.244.237.248:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 22 Oct 2026, 18:11 UTC
- hostname
- –
- first seen
- 30 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 253 on average | 107/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 242 on average | 151/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 106 on average | 34/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 58 on average | 63/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 50 on average | 46/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 48 on average | 11/250 |
Quick answers
From the figures on this page.
Population data
What position does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS take in the server rankings?
Rank #7,768 on seven-day player hours for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, within the top 35% of all ranked servers.
What population does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS carry?
Current row: 0 players on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, against 100 slots. Over the last seven days it averaged 0 players and peaked at 2.
Server facts
What does performance look like on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?
Server fps over the last 48 hours averages 132; the floor is 58. Buildings, deployables and all else in the world took the count as high as 74,823 entities. A high of 3,078 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. The protocol has to match before you can join, and Steam does the updating.
How reliable is DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, and is it online now?
Online is the state at the latest refresh for DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. Count back 6 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 30 September 2026.
Which location does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS run from?
No region is published by DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 37.244.237.248:28015 is its address.
Rules, settings, map
Which rules apply on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, and what settings?
No gather rate appears in the name: DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS loaded?
DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS runs a procedural map of size 3,500 with seed 1525560128, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS wipe, and on what schedule?
The prediction follows the tag, because DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS's wipes on record are too few to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 6 days 16 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
What is wipe day on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS like?
Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. The drop under half arrived by day 1 in the other cases.
Tags, lists
Which lists on Rust Data hold DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS, and which filters?
These Rust Data lists include DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS: Modded Rust servers and Rust PvE servers. It appears 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.
Which meanings do the tags on DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS hold?
The game's server browser reads these tags from DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into DEADROP PVE | IN-GAME MENU | RP | ZLVL | CUSTOM EVENTS?
In Rust, F1 opens the console: type client.connect 37.244.237.248:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. https://deadrop-server.duckdns.org/ is the website recorded for it.