Dragon PvE - [5x|Bots|Events]
24.66.37.218:28015 checked 12m ago
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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 24% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Sunday 18 October, 22:42 UTC, in 4d 3h. Its biweekly schedule tag · low confidence
- usual gap
- 7.3 days between real wipes
- on rhythm
- 0% of its recent wipes
- wipe-day peak
- 2 players, last three wipes
- crowd held
- 0% else halves by day 7
Coming wipes
- 4d 3hSun 18 Oct, 22:42 UTC
- 18d 3hSun 1 Nov, 22:42 UTC
- 21d 23hThu 5 Nov, 19:00 UTCFW
- 32d 3hSun 15 Nov, 22:42 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 20 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 4 Oct, 22:42 UTC 9d ago | 2 | – | running | 1 |
| Mon 21 Sep, 04:55 UTC 23d ago | 4 | halved by day 7 | 13.7 days | 0 |
| Sun 20 Sep, 07:51 UTC 24d ago | 1 | – | 0.9 days | 0 |
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 servers
Quick answers
Population
Dragon PvE - [5x|Bots|Events] ranking: what position does it hold?
In the top 24% of all ranked servers, Dragon PvE - [5x|Bots|Events] is #5,434 on player hours for the last seven days.
How many players are on Dragon PvE - [5x|Bots|Events]?
0 of 100 slots are filled on Dragon PvE - [5x|Bots|Events] at the moment. Averaged across the last seven days: 0 players, peaking at 3. Over the last 48 hours, the peak hour was 05:00 UTC, averaging 1 players.
Tags & Lists
How should the tags on Dragon PvE - [5x|Bots|Events] be interpreted?
The game's server browser reads these tags from Dragon PvE - [5x|Bots|Events]: gmvanilla (Game mode): Vanilla survival gameplay; mp100 (Max players): Slots: 100; ts8 (Group limit): Default team size: 8; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs167781 (Build): Game build number: 167781; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): No region code listed; ^b (Biweekly): Wipe cycle: biweekly; ^k (Build server): Design and practise base builds; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded, because plugins or settings modify play; oxidation (Custom tag): Set by the owner or a plugin, not a standard Rust tag. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
Who is the operator of Dragon PvE - [5x|Bots|Events]?
The dragonpve.com hostname published by Dragon PvE - [5x|Bots|Events] is used by no other server we track.
Where does Dragon PvE - [5x|Bots|Events] appear in BestRustServers.xyz lists and filters?
These BestRustServers.xyz lists include Dragon PvE - [5x|Bots|Events]: Best 5x Rust servers, Best modded Rust servers and Best Rust build servers. On the server list, the filters that bring it up are: Type: Modded; Server tag: Biweekly ^b, Build server ^k, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 5x.
Server Details
What Rust version is Dragon PvE - [5x|Bots|Events] on?
On Linux, Dragon PvE - [5x|Bots|Events] runs Rust network protocol 2634 and build 167781. Steam updates your game automatically, but it needs to match the protocol to join.
How smooth is the performance on Dragon PvE - [5x|Bots|Events]?
Over 48 hours, it averaged 106 server fps; the lowest was 85. It held up to 175,443 entities: everything from buildings to deployables in the world. Memory use peaked at 5,136 MB. Players feel lag when fps is low and entity count climbs.
What is the uptime and reliability of Dragon PvE - [5x|Bots|Events]?
The server is online: Dragon PvE - [5x|Bots|Events]. About 8 hours ago is when it last restarted, based on its uptime. It was up 100% of the time over the last 7 full days, 168 of 168 hours. On 20 September 2026, BestRustServers.xyz saw it for the first time.
What is the location of Dragon PvE - [5x|Bots|Events]?
No region is published by Dragon PvE - [5x|Bots|Events]. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. You can reach it at 24.66.37.218:28015.
Rules and Settings
Which map is used on Dragon PvE - [5x|Bots|Events]?
On Dragon PvE - [5x|Bots|Events], the map is procedural, size 4,500 with seed 1413388568, generated by the game. View it on RustMaps from this page: identical size and seed produce an identical map.
What are the settings and rules for Dragon PvE - [5x|Bots|Events]?
By its name, the gather rate is 5x on Dragon PvE - [5x|Bots|Events]. The default cap of 8 players per group is in force. It runs build & creative, no gathering: sandbox building. Plugins or settings change the game, so it appears under Modded. Plugins in use: Oxide. VAC: on.
Wipe Cycle
On what schedule does Dragon PvE - [5x|Bots|Events] wipe?
The prediction for Dragon PvE - [5x|Bots|Events] follows its tag, since too few wipes are on record to confirm its schedule. Sunday 18 October at 22:42 UTC is when the next wipe is due. Its world dates from 9 days 19 hours. A two-week wipe schedule is given in its tags.
On Dragon PvE - [5x|Bots|Events], what occurs on wipe day?
The average busiest point of its recent wipes was 2 players. 20 hours into the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 0% of its recent wipes. When it fell, the crowd dropped under half by day 7.
Connect
How can I connect to Dragon PvE - [5x|Bots|Events]?
Enter client.connect 24.66.37.218:28015 in the console (F1 in Rust), or use Launch Rust on this page to open Steam and connect. You can find its website at https://discord.com/invite/smDv2Sa.
Server tags
Published as mp100,ptrak,$r?,v2634,^b,^k,gmvanilla,cs167781,ts8,^o^z,oxidation
Game
gmvanilla- Game mode Vanilla survival gameplay.
mp100- Max players Slots: 100.
ts8- Group limit Default team size: 8.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs167781- Build Game build number: 167781.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code No region code listed.
Wipe schedule
^b- Biweekly Wipe cycle: biweekly.
Gameplay
^k- Build server Design and practise base builds.
Mods and access
^o- Oxide Plugin framework: Oxide (uMod).
^z- Modded Under Modded, because plugins or settings modify play.
Other
oxidation- Custom tag Set by the owner or a plugin, not a standard Rust tag.
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.