RUST METRICSFlight deck · live data
Data live Servers11,909 Players102,314 Populated3,972 Fresh wipes 3 h409 Scan5 min
‹ All servers95.156.238.213:10600
Offline Full Queue Fresh wipe Wipe due No query

msteryoda4evr

Offline 95.156.238.213:10600 checked 17d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,602top 71%
Last wipe18d 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, measured since 10 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
15k10k15k20k10 Oct12 Oct14 Oct15 Oct17 Oct19 Oct

Top 71% 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 peak4players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 19:55 UTC18d ago 4 – 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 happens on msteryoda4evr when wipe day comes?

At their busiest, its recent wipes drew 4 players on average. After the latest wipe, numbers topped out at 25 hours.

What wipe timing does msteryoda4evr follow?

To tell the rhythm of msteryoda4evr, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 18 days 18 hours ago the current world was made.

Tag meanings

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

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from msteryoda4evr. 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 msteryoda4evr?

These Rust Metrics lists carry msteryoda4evr: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does msteryoda4evr sit in the rankings?

Player hours over seven days put msteryoda4evr at #15,602, in the top 71% of all ranked servers.

What is the population on msteryoda4evr?

msteryoda4evr is not responding; status offline, last seen 17 days 14 hours ago.

Operator and location

What location is msteryoda4evr hosted in?

Reading: location. msteryoda4evr gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 95.156.238.213:10600.

What Rust version is msteryoda4evr on?

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

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

msteryoda4evr reports offline. The last reading came 17 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 10 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on msteryoda4evr?

Check: gather rate. The name msteryoda4evr does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on msteryoda4evr?

Size 2,600 and seed 42577913: the game generates the procedural map on msteryoda4evr from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How can you get onto msteryoda4evr?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmvanilla,cs167398,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.