Rust Server IndexCard catalogue of Rust servers

Holdings11,866 servers94,541 players396 fresh wipes

Call no.4084 On the shelf · online

Enchantress' PvE

Online 64.42.177.214:28241 checked 13m ago

Subjects 1. modded2. oxide
Players now
0/ 30
0% full
7-day average
0
peak 3
Rank
#4,084
top 18%
Last wipeWiped1 OCT2026 · 27d 21h ago
27d ago · no schedule published
Next wipe
7d 3h
Thu 5 Nov, 19:00 UTC FW
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.511.5216:0001:0010:0020:0005:0014:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

05010015020016:0001:0010:0020:0005:0014:00

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 18% of all ranked servers. Ranked on player hours over the last seven days.

Record sheet D · loan terms

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence

wipe-day peak
6players, last three wipes

Coming wipes

  1. in 7d 3hThu 5 Nov, 19:00 UTCFW
  2. in 35d 3hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 2 hours in.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
1 OCT 2026Thu 1 Oct, 18:08 UTC FW27d ago
6 – 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

ShockRust | Blue | NoLimitno group limit · 149 on average
171/ 500
EU
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
124/ 100
EU
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
186/ 225
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average
82/ 700
EU
RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average
351/ 350
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 86 on average
249/ 700
Reference desk

Quick answers

From the figures on this page.

Map and rules

What settings and rules does Enchantress' PvE run?

The name of Enchantress' PvE does not state a gather rate. The default group limit of 8 players applies. The server runs survival, gather, build and raid: the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Oxide. VAC is on: Valve's anti-cheat is enabled.

What is the map on Enchantress' PvE?

Enchantress' PvE runs a procedural map of size 4,500 with seed 2009818051, generated by the game. The map can be seen on RustMaps from this page, because the same size and seed give the same map.

Tags

Where does Enchantress' PvE appear among the Rust Server Index lists and filters?

The Rust Server Index lists that include Enchantress' PvE are Modded Rust servers, filed by play style. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the tags listed for Enchantress' PvE?

Filed under these tags, as published by Enchantress' PvE and read by the game's server browser: gmrust (Game mode): Survival on standard Rust rules; mp30 (Max players): 30 slots are available; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): The game build here is 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): No region code has been set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipe dates

How does a wipe day run on Enchantress' PvE?

At their busiest, its recent wipes drew 6 players on average. 2 hours into the latest wipe, the crowd reached its peak.

Which wipe timetable does Enchantress' PvE follow?

With the force wipe, Enchantress' PvE wipes once a month. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, taken by every Rust server. 27 days 21 hours is when its current world was made.

Players and ranking

How is Enchantress' PvE ranked compared with the rest?

On player hours over seven days, Enchantress' PvE takes #4,084, within the top 18% of ranked servers.

Is Enchantress' PvE quiet or crowded?

Enchantress' PvE is currently showing 0 players on 30 slots. Filed under seven-day figures: an average of 0 players and a peak of 3. Filed under busiest hour: 17:00 UTC in the last 48 hours, averaging 2 players.

Operator and status

What version does Enchantress' PvE use?

Rust network protocol 2635 and build 168909, on Windows, is what Enchantress' PvE runs. The protocol must match before you can join, and Steam takes care of updating it.

Is Enchantress' PvE reachable, and does it stay up?

You will find Enchantress' PvE online as of now. Its reported uptime gives the last restart as roughly 1 hours ago. Of the last 7 full days, 167 of 168 hours were up, 99% of the time. On 13 September 2026 it was first seen by Rust Server Index.

Is the performance on Enchantress' PvE good?

Averaged over the last 48 hours, server fps was 69, with a low of 44. The entity count reached 158,521, covering buildings, deployables and all else in the world. Memory use reached as much as 5,702 MB. What players feel as lag is low fps together with a rising entity count.

What is the location of Enchantress' PvE?

No region is published by Enchantress' PvE. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 64.42.177.214:28241.

Connecting

What is the way onto Enchantress' PvE?

If you would rather use the console, press F1 in Rust and enter client.connect 64.42.177.214:28241. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you. https://discord.com/invite/M5utZR32CP is where its website lives.

Subject headings explained

Server tags

What each one means.

Published as mp30,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival on standard Rust rules.
mp30
Max players 30 slots are available.
ts8
Group limit The team limit is 8, as in the standard game.
v2635
Protocol The protocol is 2635; older or newer clients cannot join.
cs168909
Build The game build here is 168909.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Modded: the game is changed by plugins or settings.

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.