ZweiMPeters Weekly Challenge
Offline 194.69.160.15:28120 checked 5d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 12:09 UTC13d ago | 1 | – | running | 0 |
| Thu 1 Oct, 10:51 UTC28d ago | 1 | halved by day 1 | 15.1 days | 0 |
| Tue 29 Sep, 09:03 UTC30d ago | 3 | held half | 2.1 days | 0 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| TheLastOfRust Hardcore PvE Zombie Survival | no group limit · 7 on average | 15 / 100 |
| Alone & Afraid | OC · no group limit · biweekly · 2 on average | 1 / 50 |
| [BR/LATAM] Evolution PVE | Hardcore Zombie Survival | SA · groups of 15+ · biweekly · 2 on average | 1 / 50 |
| TheLastOfRust Premium Hardcore PvE Zombie Survival | no group limit · 2 on average | 0 / 100 |
| ShockRust | Blue | NoLimit | no group limit · 151 on average | 23 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127 / 100 |
Quick answers
from the figures on this pageWipe cycle
On what cycle does ZweiMPeters Weekly Challenge wipe?
With irregular wipe times, ZweiMPeters Weekly Challenge offers no next wipe to predict. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 13 days 16 hours ago the current world was made.
Wipe day on ZweiMPeters Weekly Challenge: what should you expect?
The average busiest count over recent wipes is 2 players. Peak population for the latest wipe came 2 hours after it began. Above half that peak until the next wipe held in 50% of recent wipes. The fall below half arrived by day 1 when it didn't hold.
Server
In which region does ZweiMPeters Weekly Challenge sit?
The region code of ZweiMPeters Weekly Challenge is uk1, but no region is published. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 194.69.160.15:28120.
Which Rust version is ZweiMPeters Weekly Challenge on?
Rust network protocol 2634 and build 167781 on Linux is the setup for ZweiMPeters Weekly Challenge. The protocol has to match before you can join; Steam updates it automatically.
What uptime does ZweiMPeters Weekly Challenge show, and is it up?
Last seen 5 days 16 hours ago, ZweiMPeters Weekly Challenge now reports offline. Uptime over the last full days (7) was 22%, or 37 of 168 hours. It entered Rust Server Analytics records on 28 September 2026.
Tags
Which meanings do the tags on ZweiMPeters Weekly Challenge carry?
gmrust (Game mode): Rust survival, standard ruleset; mp20 (Max players): Player slots: 20; ts8 (Group limit): Team cap of 8, the stock game setting; v2634 (Protocol): Joining needs your game on protocol 2634; cs167781 (Build): Build number 167781; ptrak (Networking): Network layer: RakNet, Rust's default; $ruk1 (Region code): uk1 is the region code on record; ^h (Hardcore): Hardcore mode from Facepunch, with less help and a harsher survival loop; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play are the tags ZweiMPeters Weekly Challenge publishes, and the game's server browser reads them. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does ZweiMPeters Weekly Challenge appear across Rust Server Analytics's lists and filters?
The following Rust Server Analytics lists count ZweiMPeters Weekly Challenge among their servers: Modded Rust servers: live data. It appears on the server list under the following filters: Type: Modded; Game mode: Hardcore; Server tag: Hardcore ^h, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Player numbers
What position does ZweiMPeters Weekly Challenge hold in the server rankings?
Player hours for the last seven days place ZweiMPeters Weekly Challenge at #15,270, in the top 69% of the ranked field.
What is the population of ZweiMPeters Weekly Challenge?
ZweiMPeters Weekly Challenge is offline at this refresh; the last contact was 5 days 16 hours ago. The seven-day mean for this server is 0 players.
Settings
What settings and rules does ZweiMPeters Weekly Challenge use?
The name of ZweiMPeters Weekly Challenge does not state a gather rate. The default group cap of 8 players applies. hardcore is the game mode, Facepunch's most difficult mode. Both fighting and raiding between players are allowed. Plugins or settings modify the game, and it is listed as Modded. Oxide plugins are run. VAC, Valve's anti-cheat, is enabled.
The map on ZweiMPeters Weekly Challenge: which one is it?
A procedural map of size 3,750 with seed 1234285160, generated by the game, runs on ZweiMPeters Weekly Challenge. Size and seed fix the map, so a RustMaps view is available from this page.
How to join
How do you connect to ZweiMPeters Weekly Challenge?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 194.69.160.15:28120. Find it online at https://discord.com/invite/JCnRj3b7ND.