RUST METRICSFlight deck · live data
Data live Servers11,882 Players97,865 Populated3,914 Fresh wipes 3 h398 Scan5 min
‹ All servers219.161.1.133:28128
Offline Full Queue Fresh wipe Wipe due No query

yusutsu2107_ModServer

Offline 219.161.1.133:28128 checked 23d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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,987top 71%
Last wipe23d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 71% 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

Reset cycle

What wipe timing does yusutsu2107_ModServer follow?

To tell the rhythm of yusutsu2107_ModServer, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 23 days 3 hours ago.

Tags

How should you read the tags on yusutsu2107_ModServer?

Tags published by yusutsu2107_ModServer, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 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): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does yusutsu2107_ModServer appear in Rust Metrics lists and filters?

On Rust Metrics, yusutsu2107_ModServer sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does yusutsu2107_ModServer sit in the rankings?

Ranking for yusutsu2107_ModServer: #15,987 on seven-day player hours, top 71% of all ranked servers.

What player count does yusutsu2107_ModServer carry?

Status for yusutsu2107_ModServer: offline. Last seen 23 days 3 hours ago.

Server

What location is yusutsu2107_ModServer hosted in?

No region tag on yusutsu2107_ModServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 219.161.1.133:28128.

What Rust version is yusutsu2107_ModServer on?

Rust network protocol 2634 and build 166652 on Windows is the build yusutsu2107_ModServer runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. yusutsu2107_ModServer last answered 23 days 3 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 6 October 2026.

Map and rules

What settings and rules apply on yusutsu2107_ModServer?

Check: gather rate. The name yusutsu2107_ModServer does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is yusutsu2107_ModServer on?

Check: map. Procedural, generated by the game, on yusutsu2107_ModServer.

How to join

How can you get onto yusutsu2107_ModServer?

Press F1 in Rust and enter client.connect 219.161.1.133:28128. 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 mp2,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players 2 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build The server runs game build 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 Check: category. Modded, because plugins or settings alter the 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.