Online 195.18.27.20:35010 checked 10m ago
#2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |...
Connect
srv = rust.server("195.18.27.20:35011")
print(srv.connect_command)
Right now
srv.summary()
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 17 Sep. 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 best
Top 8% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 1h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 13, 46 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 20:15 UTC FW27d ago | 13 | NaN | running | 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.
display(srv.map, srv.info())
Operator · devilrust.ru
rust.servers(operator="devilrust.ru").sort_values("players")
| server | players | |
|---|---|---|
| 0 | #1 [PVE] DevilRust X3 | MoreEvents | RB | Eco | TP | NPC |... | 6/500 |
2 servers publish a devilrust.ru hostname.
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 | GOM 15x PVE Grumpy Old Man |Kits|Skins|BackPack|Shop|RaidableBa | NA · groups of 15+ · 15x · monthly · 46 on average | 32/115 |
| 1 | [LATAM] LUNARUST PVE X5 Mensual | 01/10 Full Wipe | SA · groups of 8+ · 5x · monthly · 42 on average | 4/100 |
| 2 | EU GOM 15x PVE Grumpy Old Man |Kits|Skins|BackPack|Shop|Raidabl | EU · groups of 15+ · 15x · monthly · 18 on average | 29/100 |
| 3 | GOM 5x PVE / With PURGE Grumpy Old Man |Kits|Skins|BackPack|Ant | NA · groups of 15+ · 5x · monthly · 7 on average | 2/100 |
| 4 | Enchanted.gg EU 10x PvE | No Raiding/Killing | Noob Friendly | EU · groups of 30+ · 10x · monthly · 6 on average | 5/50 |
| 5 | Dads Gaming Monthly 5x AU PvE - Raid Bases | Events | Kits | Sk | OC · groups of 8+ · 5x · monthly · 5 on average | 0/100 |
Quick answers
From the figures on this page.
Population
What position does #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... take in the server rankings?
Player hours over seven days put #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... at #1,780, in the top 8% of the ranked set.
How many players does #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... hold at once?
#2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... reports 2 players at this refresh, with 500 slots configured. Over the last seven days it averaged 3 players and peaked at 9. The 48-hour sample puts the busiest hour at 12:00 UTC, averaging 7 players.
Server facts
How well does #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... perform?
Averaged over 48 hours: 62 server fps, never under 53. The entity count peaked at 224,188, covering buildings, deployables and the rest of the world. A high of 6,489 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |...?
Rust network protocol 2635 and build 168909 on Windows is what #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... runs. Steam updates your game for you, but the protocol must match to join.
How reliable is #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |..., and is it up?
#2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... reports itself online at the current refresh. The uptime it reports puts the last restart about 11 hours ago. Over the last 7 full days the hours up number 161 of 168, 96%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... run from?
No region is published by #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |.... Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 195.18.27.20:35010.
Rules, settings, map
Which rules apply on #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |..., and what settings?
Gather sits at 8x, read from the server's own name: #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |.... No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |...?
Size 4,500, seed 1337: the procedural map on #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |..., generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipe schedule
When does #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... wipe, and how often?
A single wipe each month, the force wipe, is all #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 27 days 21 hours ago. The tags list wipes as monthly.
On #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |..., what happens on wipe day?
Recent wipes averaged 13 players at their peak. 46 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |..., and which filters?
On Rust Data, #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... appears in these lists: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Which operator runs #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |...?
A devilrust.ru hostname is published by #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... and by 1 other server we track, which suggests the same operator runs them.
Which meanings do the tags on #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... hold?
Read by the game's server browser, the tags #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |... publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp500 (Max players): Slot count: 500; ts8 (Group limit): The default cap applies: 8 per team; 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): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^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. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into #2 [PVE] DevilRust X8 | MoreEvents | RB | Eco | TP | NPC |...?
In Rust, F1 opens the console: type client.connect 195.18.27.20:35010. Launch Rust on this page does the same by opening the game through Steam and connecting.
