Online 46.146.234.109:10000 checked 10m ago
|PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics
Connect
srv = rust.server("46.146.234.109:10010")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 11% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 11h | Thu 12 Nov, 06:37 UTC | wipe |
| 2 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 41d 11h | Thu 10 Dec, 06:37 UTC | wipe |
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 06:37 UTC14d ago | 11 | NaN | running | 0 |
| 1 | Thu 1 Oct, 18:06 UTC FW28d ago | 12 | halved by day 8 | 13.5 days | 3 |
| 2 | 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.
display(srv.map, srv.info())Map
4500 · seed 1337
- map
- Custom Map
- size
- 4500
- seed
- 1337
Server
srv.info()- address
- 46.146.234.109:10000
- region
- –
- max players
- 200
- group limit
- 10 max
- wipe schedule
- biweekly
- last wipe
- 15 Oct 2026, 06:37 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 255 on average | 178/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 245 on average | 319/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 107 on average | 66/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 38/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 74/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 46 on average | 31/250 |
Quick answers
From the figures on this page.
Player counts
How does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics compare in the rankings?
Over the last seven days |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics sits at #2,505 on player hours, in the top 11% of ranked servers.
How full 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 reports 1 players at this refresh, with 200 slots configured. Over the last seven days it averaged 2 players and peaked at 7. The 48-hour sample puts the busiest hour at 13:00 UTC, averaging 3 players.
Server data
How smoothly does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics run?
Averaged over 48 hours: 142 server fps, never under 85. The entity count peaked at 143,313, covering buildings, deployables and the rest of the world. A high of 5,428 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?
Rust network protocol 2635 and build 168909 on Windows is what |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics, and is it up?
Online is the state at the latest refresh for |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics. A restart about 14 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics hosted?
For |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 46.146.234.109:10000 is its address.
Rules, settings, map
Which settings and rules does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics run?
Gather sits at 1x, read from the server's own name: |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics. 10 players is the maximum per group. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?
The game generates the map on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics: procedural, size 4,500, seed 1337. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.
Wipe data
When does |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics wipe, and how often?
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. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 14 days 12 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.
On |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics, what happens on wipe day?
The average peak over recent wipes is 16 players. 31 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 6.
Tags and filters
Which lists on Rust Data hold |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics, and which filters?
On Rust Data, |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics appears in these lists: Modded Rust servers 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.
Which meanings do the tags on |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics hold?
Read by the game's server browser, the tags |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics publishes are: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts10 (Group limit): Team size tops out at 10; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into |PVE|S.T.A.L.K.E.R|x1|Skill|Top|RaidBases|Statistics?
In Rust, F1 opens the console: type client.connect 46.146.234.109:10000. Launch Rust on this page does the same by opening the game through Steam and connecting. https://rust-stalker.gamestores.app is the website recorded for it.