Online 64.42.177.214:28241 checked 13m ago
Enchantress' PvE
Connect
srv = rust.server("64.42.177.214:28244")
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 bestTop 19% 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 0h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 0h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 0h | 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 6, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:08 UTC FW28d ago | 6 | 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())Map
4500 · seed 2009818051
- map
- Procedural Map
- size
- 4500
- seed
- 2009818051
Server
srv.info()- address
- 64.42.177.214:28241
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:08 UTC
- hostname
- –
- first seen
- 13 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 141/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 199/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 87/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 347/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Enchantress' PvE rank?
Over the last seven days Enchantress' PvE sits at #4,197 on player hours, in the top 19% of ranked servers.
How many players does Enchantress' PvE hold at once?
Enchantress' PvE reports 0 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 17:00 UTC, averaging 2 players.
About the server
How well does Enchantress' PvE perform?
The 48-hour average is 70 server fps, with a low of 44. Buildings, deployables and all else in the world took the count as high as 158,521 entities. The memory field tops out at 5,702 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Enchantress' PvE on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Enchantress' PvE. The protocol has to match before you can join, and Steam does the updating.
How reliable is Enchantress' PvE, and is it online now?
The current sample puts Enchantress' PvE online. The uptime it reports puts the last restart about 3 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.
Which location does Enchantress' PvE run from?
There is no region published for Enchantress' PvE. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 64.42.177.214:28241.
Settings and map
Which settings and rules does Enchantress' PvE run?
You will not find a gather rate in the string Enchantress' PvE. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Enchantress' PvE selected?
The game generates the map on Enchantress' PvE: procedural, size 4,500, seed 2009818051. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does Enchantress' PvE wipe, and on what schedule?
Once a month Enchantress' PvE wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 28 days ago.
On Enchantress' PvE, what happens on wipe day?
Recent wipes averaged 6 players at their peak. Peak population on the latest wipe came 2 hours in.
Tags and filters
Which Rust Data filters and lists contain Enchantress' PvE?
The Rust Data lists that Enchantress' PvE fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Enchantress' PvE?
These tags are published by Enchantress' PvE and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp30 (Max players): Slot count: 30; 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): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join Enchantress' PvE?
Enter client.connect 64.42.177.214:28241 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/M5utZR32CP.