StatusLive Servers online11,826 Players80,135 Populated3,731 Wiped · 3 h265 Interval5 min Date29 OCT 2026

DWG RG-S14554Server sheetchecked 30d ago

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

Offline 85.190.162.105:10200 checked 30d ago

moddedoxide
Connect
Players now 1/ 50 2% full
7-day average0peak –
Rank#14,554top 61%
Last wipe36d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]
Fig. 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 3

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.

Fig. 3Rank on player hours, daily
Schedule

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 gap1.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 22 Sep, 20:30 UTC36d ago 3 – running 1
Tue 22 Sep, 10:48 UTC37d ago 4 – 0.4 days 0
Sun 20 Sep, 13:27 UTC39d ago 1 – 1.9 days 0
Wed 16 Sep, 14:50 UTC42d ago 5 halved by day 2 3.9 days 1

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
134 / 100
02
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average
72 / 225
03
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average
77 / 700
04
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
39 / 200
05
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 85 on average
253 / 700
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
29 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime], and is it up?

The current state of [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] is offline, with the last sighting 30 days 19 hours ago. 0 of 168 hours up over the last 7 full days, which is 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

What location is recorded for [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

Europe is where the name of [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] points, with no region tag published. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 85.190.162.105:10200.

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

On Windows, [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] runs Rust network protocol 2633 and build 165217. To join, your game must be on the same protocol; Steam handles the update.

Counts

What player count is recorded on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

[GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] is not responding at the latest refresh; the last record of it online is 30 days 19 hours ago.

Against other Rust servers, where is [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] placed?

Over the last seven days, [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] records #14,554 for player hours: the top 61% of all ranked servers.

Wipe data

What happens on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] on the day of a wipe?

An average of 3 players was recorded at the busiest point of its recent wipes. 20 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 2.

What wipe schedule has been recorded for [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

No next wipe can be predicted for [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 36 days 17 hours ago.

Rules and settings

What settings and rules apply on [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

Gather rate for [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]: not stated in the name. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

On which map is [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] played?

Seed 6738 and size 3,000 define the procedural map [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

On Rust Graphs, which lists and filters contain [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

On Rust Graphs, [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime] is placed in these lists: Europe servers, plotted and Modded Rust servers. These filters on the server list return it: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

On [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime], what is meant by each tag?

The game's server browser reads these tags from [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2633 (Protocol): To join, your game must be on protocol 2633; cs165217 (Build): Build: 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

By what method do you join [GER] FEUERPAUSE [PvE/PvP | KOS-Zone RaidTime]?

Enter client.connect 85.190.162.105:10200 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players 50 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2633
Protocol To join, your game must be on protocol 2633.
cs165217
Build Build: 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code Region code not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded