RUST METRICSFlight deck · live data
Data live Servers11,777 Players67,749 Populated3,536 Fresh wipes 3 h194 Scan5 min
‹ All servers46.146.234.109:39000
Online Full Queue Fresh wipe Wipe due No query

|PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore

Online 46.146.234.109:39000 checked 11m ago

1x teams off monthly wipes moddedoxidepvehardcore
COM 1 · connect

Server instruments

last reading Thu 11:00 UTC
0 50 100 150 200 PAX 1 /200

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 93 SERVER FPS

Server fps

48 h low 74 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 240,693 ×1000

Entities

48 h range 235,546–241,196 · memory 5,066 MB
1239 ET SINCE RESTART 09:57

Uptime

9 h 57 min since its last restart, at the last reading
7-day average2peak 8
Rank#2,072top 9%
Last wipe27d agomonthly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW
Memory5,066MB48 h peak 6 players
REC 1

Players

AveragePeak
0246813:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020013:0022:0007:0016:0002:0011: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.

REC 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

force wipes only

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

wipe-day peak11players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 6hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 6hFW

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 11, 23 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:24 UTC FW27d ago 11 – running 3

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore when wipe day comes?

At their busiest, its recent wipes drew 11 players on average. Peak crowd on the latest wipe: 23 hours in.

When does |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore wipe?

With the force wipe, once a month, |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore wipes. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 27 days 18 hours ago. A monthly wipe schedule is published in its tags.

Tags

How should you read the tags on |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore?

Tags published by |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore, read by the game's server browser: gmhardcore (Game mode): A harsher set of rules: hardcore; mp200 (Max players): Slots: 200; ts0 (Group limit): Teams are off on this server; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore?

These Rust Metrics lists carry |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Modded; Game mode: PvE and Hardcore; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Wipe schedule: Monthly; Gather rate: 1x.

Occupancy

What position does |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore hold among Rust servers?

Player hours over seven days put |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore at #2,072, in the top 9% of all ranked servers.

How full does |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore get?

Current headcount on |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore: 1 players, 200 slots available. Check: players over seven days. Average 2, peak 8. The last 48 hours peaked at 19:00 UTC, averaging 6 players at that hour.

Server

Which location does |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore run from?

Reading: location. |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 46.146.234.109:39000.

What Rust version is |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore on?

Rust network protocol 2635 and build 168909 on Windows is the build |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore runs. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore?

Check: fps. Average 93 server fps over the last 48 hours, low of 74. Within range. Reading: 241,196 entities at the highest. That covers buildings, deployables and everything else. Reading: 5,768 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

Is |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore up, and how often does it stay up?

|PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore reports online. Status: normal. By its reported uptime, the last restart was roughly 9 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore enforce, and what are its settings?

Gather rate check: 1x. That comes from the name |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore. Check: group limit. None published. hardcore, Facepunch's most punishing mode — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore on?

Size 6,000: a procedural map on |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore, made by the game. Read the map name: Custom Map.

Connection

How do you connect to |PVE|S.T.A.L.K.E.R|x1-x10|XPerience|Hardcore?

Press F1 in Rust and enter client.connect 46.146.234.109:39000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,^m,^p,gmhardcore,cs168909,ts0,^o^z

Game

gmhardcore
Game mode A harsher set of rules: hardcore.
mp200
Max players Slots: 200.
ts0
Group limit Teams are off on this server.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.