RUST METRICSFlight deck · live data
Data live Servers11,751 Players55,890 Populated3,402 Fresh wipes 3 h132 Scan5 min
‹ All servers89.125.48.195:28015
Offline Full Queue Fresh wipe Wipe due No query

MODRIX_LOCAL_REVERSE_SERVER

Offline 89.125.48.195:28015 checked 39d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#14,004no region published
Last wipe39d 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
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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 timing

What wipe timing does MODRIX_LOCAL_REVERSE_SERVER follow?

To tell the rhythm of MODRIX_LOCAL_REVERSE_SERVER, 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 39 days 9 hours ago.

Tags

How should you read the tags on MODRIX_LOCAL_REVERSE_SERVER?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from MODRIX_LOCAL_REVERSE_SERVER. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show MODRIX_LOCAL_REVERSE_SERVER?

Rust Metrics lists featuring MODRIX_LOCAL_REVERSE_SERVER: 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

Where does MODRIX_LOCAL_REVERSE_SERVER sit in the rankings?

Player hours over seven days put MODRIX_LOCAL_REVERSE_SERVER at #14,004, in the top – of all ranked servers.

How full does MODRIX_LOCAL_REVERSE_SERVER get?

Status for MODRIX_LOCAL_REVERSE_SERVER: offline. Last seen 39 days 8 hours ago.

Server

Where does MODRIX_LOCAL_REVERSE_SERVER sit?

No region comes from MODRIX_LOCAL_REVERSE_SERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 89.125.48.195:28015.

What Rust version is MODRIX_LOCAL_REVERSE_SERVER on?

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

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

MODRIX_LOCAL_REVERSE_SERVER reports offline. The last reading came 39 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Settings and map

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

Reading the name gives no gather rate for MODRIX_LOCAL_REVERSE_SERVER. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.

Join

How do you connect to MODRIX_LOCAL_REVERSE_SERVER?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build The server runs game build 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.