Station EU-2950 · recording
[EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly
Online EU 185.244.0.10:25691 checked 8m ago
- Players now
- 1/ 100
- 1% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 5
- Rank
- #2,950
- top 13% · #1111 in EU
- Last wipe
- 13d ago
- biweekly schedule
- Next wipe
- 7d 6h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −2into Wed 04:00 UTC
- Peak · 48 h
- 2most 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 13% of all ranked servers, top 38% in EU, and #187 of the duo servers (top 44%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe · high confidence
- usual gap
- 28 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 4players, last three wipes
- crowd held
- 0%else halves by day 6.5
Coming wipes
- 7d 6hThu 5 Nov, 19:00 UTCFW
- 14d 1hThu 12 Nov, 13:59 UTC
- 35d 6hThu 3 Dec, 19:00 UTCFW
- 42d 1hThu 10 Dec, 13:59 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 23 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 13:59 UTC13d ago | M0.5▲rising | 3 | – | running | 0 | |
| Thu 1 Oct, 18:11 UTC FW27d ago | M0.5▲rising | 3 | halved by day 4 | 13.8 days | 0 | |
| Thu 17 Sep, 13:57 UTC41d ago | M0.8▲rising | 6 | halved by day 9 | 14.2 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 pageRules and settings
Which map is running on [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly?
The procedural map on [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly is size 4,000 with seed 1613162020, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly?
2x gather is what [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly runs, judging by its name. The limit for a group is 2 players (duo). It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly?
A reading taken now shows 1 players on [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly, which has 100 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 5. Averaged over the last 48 hours, the busiest hour was 01:00 UTC at 2 players.
How does [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly rank against other Rust servers?
The last seven days of player hours place [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly at #2,950, in the top 13% of all ranked servers and #1,111 in Europe. It sits at #187 among duo servers.
Server facts
How reliably does [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly stay online?
Right now, you can reach [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly. The uptime it reports puts its last restart about 4 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 [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly perform under load?
Its average server fps over the last 48 hours was 94, and it never dropped below 23. Buildings, deployables and all the rest of the world's entities brought it to a high of 101,715. It reached a ceiling of 3,364 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly run from?
In Europe [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly lists itself, with the tag EU. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 185.244.0.10:25691 is the address it uses.
Which Rust version is [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly running?
[EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly?
4 players, on average, was the busiest crowd at its recent wipes. 23 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 6.5.
How often does [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly wipe, and on which days?
At [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly the wipes follow a every 4 weeks on Thursday at 13:59 UTC rhythm. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 13 days 22 hours. Its tags state that it wipes every two weeks.
Tags
What do the server tags on [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly mean?
The game's server browser reads the tags [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly publishes: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): Slots: 100; ts2 (Group limit): Each team can hold up to 2; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): A wipe comes every second week; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EU (Europe): In the server browser it appears under Europe. 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 [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly appear?
You will find [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly on the following Rust Server Trends lists: 2x Rust servers, listed live, Duo Rust servers, group limit 2, EU Rust servers and Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.
Join the server
What steps get you onto [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly?
Enter client.connect 185.244.0.10:25691 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.