RUST METRICSFlight deck · live data
Data live Servers11,886 Players99,275 Populated3,950 Fresh wipes 3 h380 Scan5 min
‹ All servers194.69.160.15:28120
Offline Full Queue Fresh wipe Wipe due No query

ZweiMPeters Weekly Challenge

Offline 194.69.160.15:28120 checked 5d ago

moddedoxidehardcore
COM 1 · connect

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 0 /20

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,341top 69%
Last wipe13d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k28 Sep4 Oct10 Oct17 Oct23 Oct29 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap8.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 1

The first 48 hours of its last wipes

Fri 16 OctThu 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, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on ZweiMPeters Weekly Challenge?

The busiest point of its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 2 hours in. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. When it didn't hold, by day 1 it fell below half.

What wipe timing does ZweiMPeters Weekly Challenge follow?

There is no next wipe to predict: ZweiMPeters Weekly Challenge wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 13 days 4 hours ago the current world was made.

Lists and filters

How should you read the tags on ZweiMPeters Weekly Challenge?

Tags published by ZweiMPeters Weekly Challenge, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $ruk1 (Region code): uk1 is the region code on record; ^h (Hardcore): Hardcore mode, as Facepunch defines it: less help, tougher survival; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show ZweiMPeters Weekly Challenge?

Rust Metrics lists featuring ZweiMPeters Weekly Challenge: Modded Rust servers, checked live. These filters bring it up 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.

Player count

Where does ZweiMPeters Weekly Challenge sit in the rankings?

Player hours over seven days put ZweiMPeters Weekly Challenge at #15,341, in the top 69% of all ranked servers.

How full does ZweiMPeters Weekly Challenge get?

Reading for ZweiMPeters Weekly Challenge: offline at this moment; last seen 5 days 4 hours ago. Check: player average. 0 over the last seven days.

Operator and location

Which location does ZweiMPeters Weekly Challenge run from?

Reading: location. ZweiMPeters Weekly Challenge gives no region, with region code uk1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 194.69.160.15:28120.

What Rust version is ZweiMPeters Weekly Challenge on?

Reading: ZweiMPeters Weekly Challenge, Rust network protocol 2634 and build 167781, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is ZweiMPeters Weekly Challenge, and is it online now?

Check: connection. ZweiMPeters Weekly Challenge is offline at this moment. Last contact was 5 days 4 hours ago. Uptime for the last 7 full days: 61 of 168 hours, or 36%. Reading: first seen 28 September 2026, recorded by Rust Metrics.

Map and rules

How is ZweiMPeters Weekly Challenge configured, and what rules are in force?

Reading the name gives no gather rate for ZweiMPeters Weekly Challenge. 8 players per group, the default value. Mode check gives hardcore; Facepunch's most punishing mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is ZweiMPeters Weekly Challenge on?

From seed 1234285160, the game generates the procedural map on ZweiMPeters Weekly Challenge. Its size is 3,750. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to ZweiMPeters Weekly Challenge?

Press F1 in Rust and enter client.connect 194.69.160.15:28120. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://discord.com/invite/JCnRj3b7ND is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$ruk1,v2634,^h,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp20
Max players The server holds 20 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$ruk1
Region code uk1 is the region code on record.

Difficulty

^h
Hardcore Hardcore mode, as Facepunch defines it: less help, tougher survival.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.