RUST METRICSFlight deck · live data
Data live Servers11,851 Players93,847 Populated3,878 Fresh wipes 3 h391 Scan5 min
‹ All servers86.219.73.107:28015
Offline Full Queue Fresh wipe Wipe due No query

MykaServ

Offline 86.219.73.107:28015 checked 6d ago

COM 1 · connect

Server instruments

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

Players now

0% 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,295top 42%
Last wipe17d 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
15k10k15k20k29 Sep4 Oct14 Oct19 Oct24 Oct29 Oct

Top 42% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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
Mon 12 Oct, 12:00 UTC17d ago 1 – 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 schedule

What should you expect from wipe day on MykaServ?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

When does MykaServ wipe?

Its rhythm cannot be told from the wipes of MykaServ on record: there are too few. 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 it runs now was made 17 days 3 hours ago.

Tag meanings

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

These are the tags MykaServ publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does MykaServ appear in Rust Metrics lists and filters?

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

Player count

What position does MykaServ hold among Rust servers?

Player hours over seven days put MykaServ at #9,295, in the top 42% of all ranked servers.

What player count does MykaServ carry?

Reading for MykaServ: offline at this moment; last seen 6 days 14 hours ago. Check: players over seven days. Average 1, peak 1.

Server

Which location does MykaServ run from?

No region tag on MykaServ. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 86.219.73.107:28015.

What Rust version is MykaServ on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by MykaServ. To get in, your game needs the same protocol; Steam applies the update.

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

MykaServ reports offline. The last reading came 6 days 14 hours ago. Reading: 4% uptime over the last 7 full days. It was up 6 of 168 hours. The first sighting on Rust Metrics was 29 September 2026.

Map and rules

What rules does MykaServ enforce, and what are its settings?

Check: gather rate. The name MykaServ does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on MykaServ?

Check: map. Procedural, generated by the game, on MykaServ.

How to join

How can you get onto MykaServ?

To join: start Rust, press F1 and type client.connect 86.219.73.107: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.