An entry in the registerNo. 2,503
|PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics
Online 46.146.234.109:10000 checked 13m ago
|PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics is a Rust server. At the last count it had 0 players of a possible 200; over the past week it averaged 2, with a peak of 7. It stands at No. 2,503 of the ranked servers, the top 11%. It last wiped 14d ago, on a biweekly schedule, and the next wipe is expected on Thursday 5 November, with the force wipe. Its own tags class it as 1x, modded, oxide, pve.
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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.
§ 3Standingthe rank, daily · 1 is best
Top 11% of all ranked servers. Ranked on player hours over the last seven days.
§ 4The wipe schedulefixed weekdays
Next wipe Thursday 5 November, 19:00 UTC, in 6d 18h. The force wipe · high confidence
between real wipes
of its recent wipes
players, last three wipes
else halves by day 6
| Date, UTC | Hence |
|---|---|
| Thu 5 Nov, 19:00 FW | 6d 18h |
| Thu 12 Nov, 06:37 | 13d 6h |
| Thu 3 Dec, 19:00 FW | 34d 18h |
| Thu 10 Dec, 06:37 | 41d 6h |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 11, 31 hours in.
§ 5The record of wipesnewest first
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 06:37 UTC14d ago | 11 | – | running | 0 |
| Thu 1 Oct, 18:06 UTC FW28d 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.
§ 6In its own wordsas the server describes itself
Вайп 2 раза в месяц. Рестарт сервера в 4 утра по МСК. -- Убийства игроков отключены. -- Доступны бесплатные скины предметов и построек. -- Разрешено играть с Bloody и X7 A4tech. -- Зомби и различные боты ждут вас. -- Рейдовые базы для рейда.
§ 7Similar serversthe same kind of game, then region, group limit, rate and wipes
- 1 [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo276/2000 NA · no group limit · biweekly · 250 on average
- 2 [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo168/2000 EU · no group limit · biweekly · 242 on average
- 3 Chrayntopia ♡ ︎PvE | RP | PvP91/200 NA · groups of 8+ · biweekly · 104 on average
- 4 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能13/200 EA · groups of 16+ · biweekly · 59 on average
- 5 TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.1020/100 EU · groups of 30+ · biweekly · 49 on average
- 6 Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid56/250 groups of 8+ · biweekly · 45 on average
§ 8Questions answeredfrom the figures in this entry
Server details
What Rust version is |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics on?
The server |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics is on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, and it has to be on the same protocol to join.
How reliable is |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics, and is it online now?
The records show |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics online at the time of this check. Of note: the reported uptime places the last restart about 20 hours ago. Of note: 143 of 168 hours up in the last 7 full days, or 85% of the time. The first sighting at Rust Server Stats was on 13 September 2026.
How does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics perform?
The records show an average of 142 server fps over 48 hours, never below 85. Buildings, deployables and the rest brought the entity count to a high of 143,313. Up to 5,023 MB of memory was used. Lag, as players meet it, comes from low fps and an entity count on the rise.
Where does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics operate from?
No region is published by |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics. Rust Server Stats records the stated location of a server, not the location of the machine. At 46.146.234.109:10000 stands the address.
The rules and map
The map for |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics: which one is it?
|PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics runs a procedural map, generated by the game, of size 4,500 with seed 1337. Because size and seed fix the map, it can be viewed on RustMaps from here. The name of the map is: Custom Map.
What settings and rules does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics run?
|PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics carries a gather rate of 1x in its title. The limit for a group is 10 players. Play is pve, no combat against other players. The server browser lists it under Modded, where plugins or settings alter the game. The plugin set is Oxide. VAC, Valve's anti-cheat, is enabled.
Player record
What are the player numbers on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?
At the latest count |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics has 0 players, with 200 slots in total. Over seven days the mean is 2 players, with a peak of 7. Of the last 48 hours, 13:00 UTC drew the highest average: 3 players.
What position does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics hold among Rust servers?
The seven-day player-hour table places |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics at #2,503, within the top 11% of ranked servers.
The tags and lists
Where does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics appear among the Rust Server Stats lists and filters?
The Rust Server Stats lists |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics fits: Modded Rust servers and Rust PvE servers. On the server list it comes up under these filters: 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.
How should the tags on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics be read?
These tags are |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics's, and the game's browser reads them: gmrust (Game mode): Standard survival, as Rust plays it; mp200 (Max players): Slot count: 200; ts10 (Group limit): No team may exceed 10; v2635 (Protocol): Join only on protocol 2635; other versions cannot connect; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): The region code is not set; ^b (Biweekly): The cycle is fortnightly; ^p (PvE): No fighting between players; the world is the threat; ^o (Oxide): Oxide (uMod), a framework for plugins, runs here; ^z (Modded): Modded: settings or plugins have changed the game. The tags include current players, queue and the time the world was made; the top of this page shows them.
Wipe record
What happens on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics when wipe day arrives?
Across its recent wipes, the busiest point averaged 16 players. 31 hours into the latest wipe the crowd reached its peak. The crowd held above half the peak until the next wipe in 0% of recent wipes. By day 6, in the wipes that did not, the crowd fell below half.
On what schedule does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics wipe?
Wipes on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics follow a rhythm of every 4 weeks on Thursday at 06:37 UTC. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe shared by every Rust server. The present world dates from 14 days 17 hours. Its tags set out a fortnightly wipe schedule.
Connection
How does one connect to |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?
Join on this page with Launch Rust, which opens Rust through Steam and connects you, or open the console with F1 and enter client.connect 46.146.234.109:10000. The server's website is recorded as https://rust-stalker.gamestores.app.