RUST METRICSFlight deck · live data
Data live Servers11,841 Players77,907 Populated3,836 Fresh wipes 3 h157 Scan5 min
‹ All servers178.206.63.219:28015
Offline Full Queue Fresh wipe Wipe due No query

┬лMy

Offline 178.206.63.219:28015 checked 28d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Sep27 Sep29 Sep2 Oct4 Oct6 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.

usual gap1 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 26 SepFri 25 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 26 Sep, 20:51 UTC31d ago 1 – running 0
Fri 25 Sep, 20:06 UTC32d ago 1 – 1 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

Wipe schedule

What happens on ┬лMy when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

When does ┬лMy wipe?

To tell the rhythm of ┬лMy, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 31 days ago.

Tag meanings

How should you read the tags on ┬лMy?

These are the tags ┬лMy publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does ┬лMy appear in Rust Metrics lists and filters?

On Rust Metrics, ┬лMy sits in these lists: EU Rust servers, checked and Rust community servers: live readings. Check: filters. On the server list it appears under these: Region: Europe; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does ┬лMy hold among Rust servers?

Player hours over seven days put ┬лMy at #16,866, in the top 71% of all ranked servers.

What is the population on ┬лMy?

┬лMy is not responding; status offline, last seen 28 days 6 hours ago.

Operator and location

Where does ┬лMy sit?

The name of ┬лMy points to Europe, though it publishes no region tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 178.206.63.219:28015.

What Rust version is ┬лMy on?

Reading: ┬лMy, Rust network protocol 2633 and build 165217, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is ┬лMy up, and how often does it stay up?

Check: connection. ┬лMy is offline at this moment. Last contact was 28 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 25 September 2026.

Rules and settings

How is ┬лMy configured, and what rules are in force?

Check: gather rate. The name ┬лMy does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. 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 ┬лMy?

Check: map. Procedural, generated by the game, on ┬лMy.

Connection

What do you do to join ┬лMy?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
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.