Station XX-1614 · recording
|PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|
Online 46.146.234.109:35100 checked 9m ago
- Players now
- 0/ 200
- 0% full
- Motion · 24 h
- M0.3▼falling
- −2 players on the day
- 7-day average
- 4
- peak 11
- Rank
- #1,614
- top 7%
- Last wipe
- 14d ago
- biweekly schedule
- Next wipe
- 7d 9h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 200 slots
- Motion · 24 h
- M0.3▼falling−2 players
- Sharpest hour
- +4into Tue 15:00 UTC
- Peak · 48 h
- 11most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 7d 9h. The force wipe · high confidence
- usual gap
- 14 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 21players, last three wipes
- crowd held
- 33%else halves by day 3
Coming wipes
- 7d 9hThu 5 Nov, 19:00 UTCFW
- 13d 21hThu 12 Nov, 06:35 UTC
- 27d 21hThu 26 Nov, 06:35 UTC
- 35d 9hThu 3 Dec, 19:00 UTCFW
- 41d 21hThu 10 Dec, 06:35 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 19, 9 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 06:35 UTC14d ago | M1.2▲rising | 19 | – | running | 3 | |
| Thu 1 Oct, 18:20 UTC FW27d ago | M1.2▲rising | 18 | halved by day 2 | 13.5 days | 1 | |
| Thu 24 Sep, 06:58 UTC35d ago | M1.4▲rising | 25 | halved by day 4 | 7.5 days | 2 | |
| Thu 17 Sep, 07:04 UTC42d ago | M1.3▲rising | 22 | held half | 7 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|?
|PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| runs a procedural map of size 4,500 with seed 1337, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page. You will find the map named Custom Map.
Which settings and rules apply on |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|?
Its name points to a gather rate of 2x on |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|. Up to 10 players can be in a group. In pve mode, no combat against other players. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| right now?
At this moment, |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| records 0 players across 200 slots. The seven-day average is 4 players, with a peak of 11. The busiest point in the last 48 hours came at 15:00 UTC, averaging 9 players.
How does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| rank against other Rust servers?
The last seven days of player hours place |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| at #1,614, in the top 7% of all ranked servers.
Server facts
How reliably does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| stay online?
|PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| is up at the moment. The uptime it reports puts its last restart about 6 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
How well does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| perform under load?
Its average server fps over the last 48 hours was 113, and it never dropped below 58. At its highest, it carried 177,012 entities: buildings, deployables and the world's other contents. Its highest memory use was 5,557 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| run from?
Nothing about a region comes from |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 46.146.234.109:35100.
What build of Rust does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| use?
|PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|?
The recent wipes averaged a busiest count of 21 players. 9 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 33% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 3.
On what timetable does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| run its wipes?
The wipe rhythm at |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| is every other Thursday at 06:35 UTC. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. It has run its current world for 14 days 2 hours. Every two weeks it wipes, according to the schedule in its tags.
Lists and tags
What do the server tags on |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| mean?
The game's server browser reads the tags |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| publishes: gmrust (Game mode): The game mode is standard Rust survival; mp200 (Max players): 200 slots are available; ts10 (Group limit): Each team can hold up to 10; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^b (Biweekly): A wipe comes every second week; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| appear?
You will find |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| on the following Rust Server Trends lists: 2x Rust servers, listed live, Modded Rust servers, tracked 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: 2x.
Connecting
What steps get you onto |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|?
To join, enter client.connect 46.146.234.109:35100 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://vk.ru/stalkerris.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.