RUST METRICSFlight deck · live data
Data live Servers11,682 Players54,903 Populated3,147 Fresh wipes 3 h122 Scan5 min
‹ All servers133.202.226.217:28015
Offline Full Queue Fresh wipe Wipe due No query

MIZUMIZU

Offline 133.202.226.217:28015 checked 26d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 0 /20

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#16,004top 70%
Last wipe26d 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
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

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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 15:39 UTC26d ago 0 – 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

Reset cycle

What happens on MIZUMIZU when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does MIZUMIZU follow?

To tell the rhythm of MIZUMIZU, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 26 days 9 hours ago.

Tags

How should you read the tags on MIZUMIZU?

Tags published by MIZUMIZU, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): Slots: 20; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show MIZUMIZU?

On Rust Metrics, MIZUMIZU sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

Where does MIZUMIZU sit in the rankings?

Player hours over seven days put MIZUMIZU at #16,004, in the top 70% of all ranked servers.

How full does MIZUMIZU get?

Status for MIZUMIZU: offline. Last seen 26 days 9 hours ago.

Operator and location

What location is MIZUMIZU hosted in?

Reading: location. MIZUMIZU gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 133.202.226.217:28015.

What Rust version is MIZUMIZU on?

Rust network protocol 2634 and build 166652 on Windows is the build MIZUMIZU runs. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. MIZUMIZU is offline at this moment. Last contact was 26 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 3 October 2026.

Map and rules

What settings and rules apply on MIZUMIZU?

Reading the name gives no gather rate for MIZUMIZU. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on MIZUMIZU?

The game generates a procedural map for MIZUMIZU.

Join

How do you connect to MIZUMIZU?

Press F1 in Rust and enter client.connect 133.202.226.217:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp20
Max players Slots: 20.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.