Rust Server TrendsSeismic network · station log
Recording Stations11,715 Players57,218 Active3,311 Wipes · 3 h174 48 h

Station XX-14554 · no signal

[GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]

Offline 85.190.162.105:10200 checked 30d ago

moddedoxide
Connect
Players now
1/ 50
2% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,554
top 61%
Last wipe
36d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-14554 · 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
1of 50 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 17 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
15k10k15k20k20 Sep23 Sep26 Sep29 Sep2 Oct5 Oct

Top 61% 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
1.9 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
0%else halves by day 2

The first 48 hours of its last wipes

Tue 22 SepTue 22 SepSun 20 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 20 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 22 Sep, 20:30 UTC36d ago M0.3rising 3 – running 1
Tue 22 Sep, 10:48 UTC36d ago M0.6rising 4 – 0.4 days 0
Sun 20 Sep, 13:27 UTC38d ago M0.0rising 1 – 1.9 days 0
Wed 16 Sep, 14:50 UTC42d ago M0.6rising 5 halved by day 2 3.9 days 1

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
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
188/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
77/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
9/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
19/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 81 on average
229/ 700
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

The procedural map on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] is size 3,000 with seed 6738, 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 [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

No gather rate appears in the name of [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

A reading taken now finds [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] offline; the most recent activity was 30 days 15 hours ago.

How does [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] rank against other Rust servers?

The last seven days of player hours place [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] at #14,554, in the top 61% of all ranked servers.

Server details

How reliably does [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] stay online?

[GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] is down at the moment; the last recorded contact was 30 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] hosted?

No region tag comes from [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime], though the name points to Europe. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 85.190.162.105:10200.

Which Rust version is [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] running?

Rust network protocol 2633 and build 165217 on Windows is what [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

The recent wipes averaged a busiest count of 3 players. 20 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2 it fell below half in the wipes where it didn't hold.

How often does [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] wipe, and on which days?

No next wipe can be predicted for [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime], which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 36 days 14 hours is how long the current world has been running.

Server tags

What do the server tags on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] mean?

These are the tags [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] publishes for the browser to read: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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 [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] appear?

These Rust Server Trends lists include [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]: EU Rust servers and Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

To join, enter client.connect 85.190.162.105:10200 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs165217,ts8,^o^z

Game

gmvanilla
Game mode This is vanilla survival.
mp50
Max players 50 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build Game build: 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it 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.