RUST METRICSFlight deck · live data
Data live Servers11,647 Players32,606 Populated2,787 Fresh wipes 3 h74 Scan5 min
‹ All servers138.16.248.202:28015
Offline Full Queue Fresh wipe Wipe due No query

MyServer (TEST)

Offline 138.16.248.202:28015 checked 2d ago

moddedoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 1 /100

Players now

1% full 7-day avg7-day peak
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 average1peak 1
Rank#9,899top 44%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k15 Oct18 Oct21 Oct23 Oct26 Oct29 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap5.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Mon 26 OctSat 17 OctFri 16 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 16:09 UTC2d ago 1 – running 0
Sat 17 Oct, 04:52 UTC11d ago 1 halved by day 2 9.5 days 1
Fri 16 Oct, 04:41 UTC12d ago 1 – 1 days 1

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 schedule

What should you expect from wipe day on MyServer (TEST)?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 2 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2 it fell below half when it didn't.

What wipe timing does MyServer (TEST) follow?

No next wipe can be predicted for MyServer (TEST), which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 2 days 12 hours ago the current world was made.

Tag meanings

How should you read the tags on MyServer (TEST)?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): 100 slots in total; ts10 (Group limit): Team cap: 10; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from MyServer (TEST). Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show MyServer (TEST)?

Rust Metrics lists featuring MyServer (TEST): Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Population

Where does MyServer (TEST) sit in the rankings?

Player hours over seven days put MyServer (TEST) at #9,899, in the top 44% of all ranked servers.

What is the population on MyServer (TEST)?

MyServer (TEST) is not responding; status offline, last seen 2 days 7 hours ago. Check: players over seven days. Average 1, peak 1.

Server

What location is MyServer (TEST) hosted in?

No region tag on MyServer (TEST). Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 138.16.248.202:28015.

What Rust version is MyServer (TEST) on?

Rust network protocol 2635 and build 168909 on Windows is the build MyServer (TEST) runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on MyServer (TEST), and is it online?

Reading: offline. MyServer (TEST) last answered 2 days 7 hours ago. Uptime for the last 7 full days: 4 of 168 hours, or 2%. Check: first contact. Rust Metrics logged it on 15 October 2026.

Map and rules

What rules does MyServer (TEST) enforce, and what are its settings?

Check: gather rate. The name MyServer (TEST) does not state one. The cap on groups is 10 players. pve, fighting between players is off — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is off.

How to join

How do you connect to MyServer (TEST)?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^p,gmvanilla,cs168909,ts10,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp100
Max players 100 slots in total.
ts10
Group limit Team cap: 10.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.