Rust Server TrendsSeismic network · station log
Recording Stations11,875 Players94,751 Active3,875 Wipes · 3 h395 48 h

Station UK-15344 · no signal

ZweiMPeters Weekly Challenge

Offline 194.69.160.15:28120 checked 5d ago

moddedoxidehardcore
Connect
Players now
0/ 20
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,344
top 69%
Last wipe
13d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station UK-15344 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 20 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 gap
8.6 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
50%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 12:09 UTC13d ago M0.0rising 1 – running 0
Thu 1 Oct, 10:51 UTC28d ago M0.0rising 1 halved by day 1 15.1 days 0
Tue 29 Sep, 09:03 UTC30d ago M0.5rising 3 held half 2.1 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
TheLastOfRust Hardcore PvE Zombie Survival no group limit · 7 on average
2/ 100
Nikki & Yuni Hardcore Solo/Duo | Wiped 10/15 | No Tech Tree | R NA · no group limit · biweekly · 3 on average
2/ 50
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
2/ 50
0/ 100
ほしラス2 EA · no group limit · 1 on average
1/ 50
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on ZweiMPeters Weekly Challenge?

Generated by the game, the map on ZweiMPeters Weekly Challenge is procedural, size 3,750 with seed 1234285160. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on ZweiMPeters Weekly Challenge?

No gather rate appears in the name of ZweiMPeters Weekly Challenge. At the game's default, groups can have up to 8 players. It plays in hardcore mode, Facepunch's most punishing mode. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on ZweiMPeters Weekly Challenge?

No players are recorded on ZweiMPeters Weekly Challenge at this moment; it is offline, and the last sighting was 5 days 3 hours ago. The seven-day average for this server is 0 players.

How does ZweiMPeters Weekly Challenge rank against other Rust servers?

Over the last seven days, ZweiMPeters Weekly Challenge recorded enough player hours to reach #15,344 worldwide, placing it in the top 69% of all ranked servers.

Operator and location

How reliably does ZweiMPeters Weekly Challenge stay online?

No contact with ZweiMPeters Weekly Challenge right now, and the last recorded contact was 5 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 61, or 36% of the time. Its earliest appearance in the records of Rust Server Trends dates to 28 September 2026.

Which region does ZweiMPeters Weekly Challenge run from?

Its region code is uk1, and ZweiMPeters Weekly Challenge publishes no region. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 194.69.160.15:28120.

What build of Rust does ZweiMPeters Weekly Challenge use?

ZweiMPeters Weekly Challenge is running Rust network protocol 2634 and build 167781 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on ZweiMPeters Weekly Challenge?

On average, the busiest point of its recent wipes drew 2 players. 2 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 50% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.

How often does ZweiMPeters Weekly Challenge wipe, and on which days?

There is no next wipe to predict at ZweiMPeters Weekly Challenge, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 13 days 3 hours is how long the current world has been running.

Server tags

What do the server tags on ZweiMPeters Weekly Challenge mean?

Tags published by ZweiMPeters Weekly Challenge and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp20 (Max players): The server has 20 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): Game build: 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $ruk1 (Region code): The region code for this server is uk1; ^h (Hardcore): Hardcore, as Facepunch defines it: less help, survival is harsher; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does ZweiMPeters Weekly Challenge appear?

These Rust Server Trends lists include ZweiMPeters Weekly Challenge: Modded Rust servers, tracked live. You will find it 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.

Connecting

What steps get you onto ZweiMPeters Weekly Challenge?

Enter client.connect 194.69.160.15:28120 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. https://discord.com/invite/JCnRj3b7ND is where its website lives.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp20
Max players The server has 20 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build Game build: 167781.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$ruk1
Region code The region code for this server is uk1.

Difficulty

^h
Hardcore Hardcore, as Facepunch defines it: less help, survival is harsher.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

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.