RUST METRICSFlight deck · live data
Data live Servers11,695 Players53,611 Populated3,212 Fresh wipes 3 h134 Scan5 min
‹ All servers85.10.198.210:28015
Online Full Queue Fresh wipe Wipe due No query

Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep

Online 85.10.198.210:28015 checked 12m ago

biweekly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Thu 08:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 124 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 324,079 ×1000

Entities

48 h range 323,655–324,191 · memory 4,230 MB
1239 ET SINCE RESTART 15D 07H

Uptime

15 days 7 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,338top 69%
Last wipe510d agobiweekly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Memory4,230MBat the last reading
REC 1

Players

AveragePeak
0123411:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020011:0020:0005:0013:0023:0008: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 17 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

Wipe schedule

How often does Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep wipe, and when?

The estimate for Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep's next wipe comes from the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 510 days 12 hours ago. A wipe schedule of every two weeks is published in its tags.

Tags

Which tags does Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep carry, and what do they mean?

Tags published by Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp100 (Max players): 100 slots in total; v2590 (Protocol): Match the game version: protocol 2590 is required; cs122868 (Build): Game build reading: 122868; ptrak (Networking): This is RakNet, Rust's usual network layer; $rger (Region code): Region code reading: ger; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^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.

Where does Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Wipe schedule: Every two weeks.

Player count

Where does Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep sit in the rankings?

Player hours over seven days put Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep at #15,338, in the top 69% of all ranked servers.

What player count does Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep carry?

Current headcount on Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep: 0 players, 100 slots available. A seven-day average of 0 players is the reading.

Operator and location

Which location does Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep run from?

No region comes from Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep, and its region code is ger. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 85.10.198.210:28015.

What Rust version is Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep on?

Version check: Rust network protocol 2590 and build 122868 on Windows, run by Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep. Matching protocol is required to join. Let Steam update your game.

Is performance on Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep within range?

Reading: 152 server fps on average across the last 48 hours. It never dropped below 124. Check: entities. The peak was 324,191, counting buildings, deployables and the rest of the world. Memory peak: 4,702 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep, and is it online now?

Reading: online. Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep answers right now. Reading: uptime. About 15 days 7 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep enforce, and what are its settings?

Check: gather rate. The name Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep does not state one. The group limit is not published. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. The server calls itself vanilla, with this meaning: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep?

From seed 76951874, the game generates the procedural map on Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to Mitternacht 2.0 | Raid-Time | KOS-Zones | Low Upkeep?

To join: start Rust, press F1 and type client.connect 85.10.198.210:28015. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/j8VF6mUAHV is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$rger,v2590,^b,^v,gmvanilla,cs122868,^o^z

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp100
Max players 100 slots in total.
v2590
Protocol Match the game version: protocol 2590 is required.
cs122868
Build Game build reading: 122868.
ptrak
Networking This is RakNet, Rust's usual network layer.
$rger
Region code Region code reading: ger.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^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.