Skip to the page
RUST ANALYTICS
LIVE76,128PLY11,718SRV
QUOTE 194.69.160.15:28120 Online checked 9m ago

ZweiMPeters Weekly Challenge

moddedoxidehardcore
Players · last
0/ 20
+024h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
0/ 20
0% full
Change · 24h
+0
no reading a day ago
7-day average
0
peak –
Rank
#15,892
top 72%
Rank · 7d ago
#15,278
614 places down
Last wipe
13d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
0
player hours, last seven days
Map
4000
Procedural Map · seed 1851552942
First seen
28 Sep 2026
no hostname published

Players

AveragePeak
0123420:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

Server performance

02040608020:0005:0014:0000:0009:0018:00

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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k28 Sep1 Oct4 Oct8 Oct11 Oct14 Oct

Top 72% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap
2.1 days
between real wipes
wipe-day peak
2
players, last three wipes
crowd held
100%
of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 1 OctTue 29 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 10:51 UTC13d ago 1 – running 0
Tue 29 Sep, 09:03 UTC15d 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1TheLastOfRust Hardcore PvE Zombie Survivalno group limit · 7 on average7/100+1+13.5%
2Blackland#001 | Hardcore | ARE YOU STRONG ENOUGHNA · no group limit · monthly · 3 on average3/100+0−14.3%
3Stumpy Hardcore Solo Only | No Tech Tree | Raid WindowNA · no group limit · biweekly · 3 on average4/50−1−18.6%
4Server hosted by Physgun.comNA · no group limit · 2 on average1/100+0−33.3%
5[BR/LATAM] Evolution PVE | Hardcore Zombie SurvivalSA · groups of 15+ · biweekly · 1 on average1/50+1
6Grandpa Rust TRUE Hardcore - BP WHAT YOU FIND- NO Tech Tree [U.no group limit · monthly · 1 on average2/50+2

Quick answers

from the figures on this page

Map and Rules

What settings and rules are in place on ZweiMPeters Weekly Challenge?

No gather rate is given in the name of ZweiMPeters Weekly Challenge. Groups can contain a maximum of 8 players, the default for the game. It runs hardcore, Facepunch's hardest mode. PvP and raiding are enabled. In the server browser it appears under Modded, with plugins or settings that change the game. Plugin count: Oxide. VAC is active.

What is the current map on ZweiMPeters Weekly Challenge?

ZweiMPeters Weekly Challenge uses a procedural map of size 4,000 with seed 1851552942, generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Activity

What is the rank of ZweiMPeters Weekly Challenge?

For the last seven days, ZweiMPeters Weekly Challenge holds rank #15,892 on player hours, in the top 72% of all ranked servers.

What is the population on ZweiMPeters Weekly Challenge?

On ZweiMPeters Weekly Challenge, 0 players are in now, out of 20 slots. Average players over the last seven days: 0.

Wipe Cycle

How does ZweiMPeters Weekly Challenge handle wipe day?

An average of 2 players marked the busiest point of its recent wipes. On the latest wipe, 4 hours after the wipe, the crowd peaked. Half the peak was held until the next wipe in 100% of its recent wipes.

How often does ZweiMPeters Weekly Challenge wipe?

The record holds too few of ZweiMPeters Weekly Challenge's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. Its world now is 13 days 9 hours old.

Server Overview

What is the location of ZweiMPeters Weekly Challenge?

No region from ZweiMPeters Weekly Challenge, and its region code is uk1. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 194.69.160.15:28120 is its address.

What is the performance like on ZweiMPeters Weekly Challenge?

Average server fps for the last 48 hours is 56; the floor was 56. 94,238 entities is the maximum carried: buildings, deployables and everything else. Memory use peaked at 5,083 MB. A climbing entity count plus low fps is the lag players report.

ZweiMPeters Weekly Challenge is on which Rust version?

Rust network protocol 2633 and build 165217 on Linux is what ZweiMPeters Weekly Challenge runs. Your game needs the same protocol to get in; Steam takes care of the update.

What is the uptime and reliability of ZweiMPeters Weekly Challenge?

ZweiMPeters Weekly Challenge is up. It is taking players now. Its own uptime figure dates the last restart to roughly 13 days 7 hours ago. 100% is its uptime for the last 7 full days, 168 of 168 hours. 28 September 2026 is when Rust Analytics first saw it.

Tags and Rankings

What is the meaning of the tags on ZweiMPeters Weekly Challenge?

The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp20 (Max players): It holds 20 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2633 (Protocol): Your game must run protocol 2633 to connect; cs165217 (Build): Build 165217; ptrak (Networking): RakNet, the network layer the game ships with; $ruk1 (Region code): The region code reads uk1; ^h (Hardcore): The hardcore ruleset from Facepunch: fewer helpers, harder survival; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings, which ZweiMPeters Weekly Challenge publishes. Also in the tags and at the top of this page: current players, queue and world creation time.

Where does ZweiMPeters Weekly Challenge show up in Rust Analytics lists and filters?

These Rust Analytics lists include ZweiMPeters Weekly Challenge: Modded Rust servers. It appears under these filters on the server list: 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.

Joining the Server

What is the process to join ZweiMPeters Weekly Challenge?

Type client.connect 194.69.160.15:28120 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you. You can visit its website at https://discord.com/invite/JCnRj3b7ND.

Server tags

what each one means

Published as mp20,ptrak,$ruk1,v2633,^h,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp20
Max players It holds 20 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2633
Protocol Your game must run protocol 2633 to connect.
cs165217
Build Build 165217.
ptrak
Networking RakNet, the network layer the game ships with.
$ruk1
Region code The region code reads uk1.

Difficulty

^h
Hardcore The hardcore ruleset from Facepunch: fewer helpers, harder survival.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.