RUST METRICSFlight deck · live data
Data live Servers11,892 Players102,135 Populated3,937 Fresh wipes 3 h401 Scan5 min
‹ All servers46.146.234.109:10000
Online Full Queue Fresh wipe Wipe due No query

|PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics

Online 46.146.234.109:10000 checked 10m ago

1x biweekly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 16: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 119 SERVER FPS

Server fps

48 h low 85 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 143,313 ×1000

Entities

48 h range 132,971–143,313 · memory 4,354 MB
1239 ET SINCE RESTART 14:57

Uptime

14 h 57 min since its last restart, at the last reading
7-day average2peak 7
Rank#2,525top 11%
Last wipe14d agobiweekly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW
Memory4,354MB48 h peak 4 players
REC 1

Players

AveragePeak
0123418:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020018:0003:0012:0022:0007:0016: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 11% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

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

usual gap28 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak16players, last three wipes
crowd held0%else halves by day 6

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 1hFW
  2. WPT 2Thu 12 Nov, 06:37 UTC13d 13h
  3. WPT 3Thu 3 Dec, 19:00 UTC35d 1hFW
  4. WPT 4Thu 10 Dec, 06:37 UTC41d 13h

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctThu 17 Sep
010203040+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 06:37 UTC14d ago 11 – running 0
Thu 1 Oct, 18:06 UTC FW27d ago 12 halved by day 8 13.5 days 3
Thu 17 Sep, 06:59 UTC42d ago 26 halved by day 4 14.5 days 1

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

Reset cycle

What should you expect from wipe day on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?

At their busiest, its recent wipes drew 16 players on average. After the latest wipe, numbers topped out at 31 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 6 it fell below half when it didn't.

How often does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics wipe, and when?

every 4 weeks on Thursday at 06:37 UTC is how |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics wipes. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 14 days 10 hours ago. A wipe schedule of every two weeks is published in its tags.

Lists and filters

How should you read the tags on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?

These are the tags |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): Slots: 200; ts10 (Group limit): Team cap: 10; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^b (Biweekly): It wipes once a fortnight; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics appear in Rust Metrics lists and filters?

Rust Metrics lists featuring |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 1x.

Occupancy

Where does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics sit in the rankings?

Ranking for |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics: #2,525 on seven-day player hours, top 11% of all ranked servers.

How full does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics get?

1 of 200 slots are filled on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics right now. Check: players over seven days. Average 2, peak 7. The last 48 hours peaked at 13:00 UTC, averaging 3 players at that hour.

Server details

Which location does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics run from?

Reading: location. |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 46.146.234.109:10000.

What Rust version is |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics on?

Reading: |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?

Check: fps. Average 143 server fps over the last 48 hours, low of 85. Within range. Check: entities. The peak was 143,313, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 5,578 MB. Expect lag when fps falls and entities climb.

How reliable is |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics, and is it online now?

|PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 14 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?

The name carries the rate: 1x gather on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics. The cap on groups is 10 players. pve, no combat against other players — that is the game mode. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

What map is |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics on?

From seed 1337, the game generates the procedural map on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics. Its size is 4,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name Custom Map.

Connection

How do you connect to |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?

Press F1 in Rust and enter client.connect 46.146.234.109:10000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://rust-stalker.gamestores.app.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,^b,^p,gmrust,cs168909,ts10,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players Slots: 200.
ts10
Group limit Team cap: 10.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Gameplay

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

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.