RUST METRICSFlight deck · live data
Data live Servers11,875 Players97,136 Populated3,915 Fresh wipes 3 h398 Scan5 min
‹ All servers87.148.198.108:54412
Offline Full Queue Fresh wipe Wipe due No query

Eisenoxid

Offline 87.148.198.108:54412 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,993top 70%
Last wipe33d agono schedule published
Next wipe–no wipe seen yet
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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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 Eisenoxid wipe, and when?

Its rhythm cannot be told from the wipes of Eisenoxid on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 33 days 19 hours ago.

Tags

How should you read the tags on Eisenoxid?

Tags published by Eisenoxid, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Eisenoxid appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Eisenoxid: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Eisenoxid hold among Rust servers?

Ranking for Eisenoxid: #15,993 on seven-day player hours, top 70% of all ranked servers.

How full does Eisenoxid get?

Reading for Eisenoxid: offline at this moment; last seen 26 days 7 hours ago.

Server details

What location is Eisenoxid hosted in?

No region comes from Eisenoxid. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 87.148.198.108:54412.

What Rust version is Eisenoxid on?

Rust network protocol 2633 and build 165217 on Linux is the build Eisenoxid runs. Check: protocol. To join, your game must match; Steam handles the update.

Is Eisenoxid up, and how often does it stay up?

Check: connection. Eisenoxid is offline at this moment. Last contact was 26 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 3 October 2026.

Rules and settings

How is Eisenoxid configured, and what rules are in force?

No gather rate appears in the name: Eisenoxid. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is Eisenoxid on?

Size 3,500 and seed 50: the game generates the procedural map on Eisenoxid from them. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How do you connect to Eisenoxid?

To join: start Rust, press F1 and type client.connect 87.148.198.108:54412. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players The server holds 5 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.