RUST METRICSFlight deck · live data
Data live Servers11,689 Players60,760 Populated3,467 Fresh wipes 3 h117 Scan5 min
‹ All servers1.147.93.99:28015
Offline Full Queue Fresh wipe Wipe due No query

MITTENZONLY

Offline 1.147.93.99:28015 checked 17d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,863top 72%
Last wipe24d agono schedule published
Next wipe–too few wipes 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct4 Oct7 Oct11 Oct14 Oct17 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 05:05 UTC24d ago 1 – running 0

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 timing

What should you expect from wipe day on MITTENZONLY?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does MITTENZONLY wipe, and when?

The rhythm of MITTENZONLY's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 24 days 6 hours ago.

Tag meanings

Which tags does MITTENZONLY carry, and what do they mean?

Tags published by MITTENZONLY, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp1 (Max players): Slots: 1; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167058 (Build): The server runs game build 167058; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does MITTENZONLY appear in Rust Metrics lists and filters?

Rust Metrics lists featuring MITTENZONLY: 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 MITTENZONLY hold among Rust servers?

Player hours over seven days put MITTENZONLY at #15,863, in the top 72% of all ranked servers.

What is the population on MITTENZONLY?

MITTENZONLY is not responding; status offline, last seen 17 days 20 hours ago.

Server details

What location is MITTENZONLY hosted in?

No region tag on MITTENZONLY. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 1.147.93.99:28015.

What Rust version is MITTENZONLY on?

Reading: MITTENZONLY, Rust network protocol 2634 and build 167058, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on MITTENZONLY, and is it online?

Reading: offline. MITTENZONLY last answered 17 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does MITTENZONLY enforce, and what are its settings?

No gather rate appears in the name: MITTENZONLY. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on MITTENZONLY?

The game generates a procedural map for MITTENZONLY.

Connection

How do you connect to MITTENZONLY?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmvanilla,cs167058,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp1
Max players Slots: 1.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167058
Build The server runs game build 167058.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.