RUST METRICSFlight deck · live data
Data live Servers11,662 Players43,563 Populated3,033 Fresh wipes 3 h101 Scan5 min
‹ All servers176.37.49.95:28015
Offline Full Queue Fresh wipe Wipe due No query

MIKOSERVER

Offline 176.37.49.95:28015 checked 3d ago

COM 1 · connect

Server instruments

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

Players now

10% 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#12,470top 56%
Last wipe3d 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 25 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
15k10k15k20k24 Sep26 Sep28 Sep1 Oct26 Oct28 Oct

Top 56% 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 gap30.3 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sun 25 OctThu 24 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
Sun 25 Oct, 00:27 UTC3d ago 1 – running 1
Thu 24 Sep, 16:19 UTC33d ago 1 – 30.3 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 timing

What happens on MIKOSERVER when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does MIKOSERVER follow?

Its rhythm cannot be told from the wipes of MIKOSERVER 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 in play was created 3 days 1 hours ago.

Tag meanings

How should you read the tags on MIKOSERVER?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from MIKOSERVER. 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 MIKOSERVER?

Rust Metrics lists featuring MIKOSERVER: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Population

Where does MIKOSERVER sit in the rankings?

Player hours over seven days put MIKOSERVER at #12,470, in the top 56% of all ranked servers.

How full does MIKOSERVER get?

Status for MIKOSERVER: offline. Last seen 3 days ago. Seven-day check: 1 players on average. Peak reading: 1.

Server details

Which location does MIKOSERVER run from?

Reading: location. MIKOSERVER gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 176.37.49.95:28015.

What Rust version is MIKOSERVER on?

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

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

Reading: offline. MIKOSERVER last answered 3 days ago. Reading: 1% uptime over the last 7 full days. It was up 2 of 168 hours. The first sighting on Rust Metrics was 24 September 2026.

Settings and map

What settings and rules apply on MIKOSERVER?

No gather rate appears in the name: MIKOSERVER. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is MIKOSERVER on?

Check: map. Procedural, size 5,000, seed 1337, generated by the game on MIKOSERVER. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.

How to join

How do you connect to MIKOSERVER?

Check: join. Open Rust, press F1, then enter client.connect 176.37.49.95:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://www.youtube.com/@mikonine.?cbrd=1&ucbcb=1 is where its website sits.

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 Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.