Station XX-4045 · recording
Enchantress' PvE
Online 64.42.177.214:28241 checked 8m ago
- Players now
- 0/ 30
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 3
- Rank
- #4,045
- top 18%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- 7d 5h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 30 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −2into Wed 19:00 UTC
- Peak · 48 h
- 2most players in any hour
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 5h. The force wipe · high confidence
- wipe-day peak
- 6players, last three wipes
Coming wipes
- 7d 5hThu 5 Nov, 19:00 UTCFW
- 35d 5hThu 3 Dec, 19:00 UTCFW
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 18:08 UTC FW27d ago | M0.8▲rising | 6 | – | running | 0 |
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 pageRules and settings
Which map is running on Enchantress' PvE?
Generated by the game, the map on Enchantress' PvE is procedural, size 4,500 with seed 2009818051. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Enchantress' PvE?
No gather rate appears in the name of Enchantress' PvE. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on Enchantress' PvE right now?
A reading taken now shows 0 players on Enchantress' PvE, which has 30 slots. The seven-day average is 1 players, with a peak of 3. The last 48 hours show their highest activity at 17:00 UTC, averaging 2 players.
How does Enchantress' PvE rank against other Rust servers?
Over the last seven days, Enchantress' PvE recorded enough player hours to reach #4,045 worldwide, placing it in the top 18% of all ranked servers.
Server facts
How reliably does Enchantress' PvE stay online?
Enchantress' PvE is up at the moment. Its reported uptime points to a restart about 23 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
How well does Enchantress' PvE perform under load?
Across the last 48 hours it averaged 68 server fps, with a floor of 44. At its highest, it carried 158,521 entities: buildings, deployables and the world's other contents. Memory use peaked at 5,702 MB. Low fps together with a growing entity count is what players experience as lag.
Where in the world is Enchantress' PvE hosted?
A region is not published by Enchantress' PvE. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 64.42.177.214:28241.
What build of Rust does Enchantress' PvE use?
On Windows, Enchantress' PvE runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Enchantress' PvE?
The recent wipes averaged a busiest count of 6 players. 2 hours after the latest wipe, the crowd peaked.
On what timetable does Enchantress' PvE run its wipes?
The force wipe is the only wipe Enchantress' PvE takes, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 27 days 19 hours.
Lists and tags
What do the server tags on Enchantress' PvE mean?
The game's server browser reads the tags Enchantress' PvE publishes: gmrust (Game mode): The game mode is standard Rust survival; mp30 (Max players): 30 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Enchantress' PvE appear?
The Rust Server Trends lists that take in Enchantress' PvE are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto Enchantress' PvE?
To join, enter client.connect 64.42.177.214:28241 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://discord.com/invite/M5utZR32CP.
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.