RUST METRICSFlight deck · live data
Data live Servers11,772 Players62,070 Populated3,548 Fresh wipes 3 h127 Scan5 min
‹ All servers213.33.145.103:28015
Offline Full Queue Fresh wipe Wipe due No query

My_Server

Offline 213.33.145.103:28015 checked 14d ago

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#15,249top 70%
Last wipe–no 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
15k10k15k20k24 Sep29 Sep5 Oct10 Oct16 Oct21 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.

usual gap13.4 daysbetween real wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 8 OctThu 24 Sep
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 06:31 UTC20d ago 0 – running 0
Thu 24 Sep, 22:00 UTC34d ago 1 halved by day 1 13.4 days 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 My_Server when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 1 it fell below half when it didn't.

What wipe timing does My_Server follow?

The rhythm of My_Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one.

Tags

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

These are the tags My_Server publishes, and the server browser reads them: 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; cs166586 (Build): Build 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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 My_Server?

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

Occupancy

Where does My_Server sit in the rankings?

Player hours over seven days put My_Server at #15,249, in the top 70% of all ranked servers.

How full does My_Server get?

Status for My_Server: offline. Last seen 14 days 6 hours ago.

Operator and location

Where does My_Server sit?

No region tag on My_Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 213.33.145.103:28015.

What Rust version is My_Server on?

Version check: Rust network protocol 2634 and build 166586 on Linux, run by My_Server. Matching protocol is required to join. Let Steam update your game.

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

My_Server reports offline. The last reading came 14 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 24 September 2026, recorded by Rust Metrics.

Settings and map

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

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

How to join

What do you do to join My_Server?

Check: join. Open Rust, press F1, then enter client.connect 213.33.145.103:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs166586,ts8

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.
cs166586
Build Build 166586.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.