Skip to the page
RUST ANALYTICS
LIVE31,970PLY11,447SRV
QUOTE 150.251.143.217:28015 Offline checked 9d ago

MIHA

Players · last
0/ 2
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 2
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#15,988
top 71%
Rank · 7d ago
#13,600
2388 places down
Last wipe
9d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
0
player hours, last seven days
Map
–
Procedural Map
First seen
3 Oct 2026
no hostname published

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct5 Oct7 Oct8 Oct10 Oct12 Oct

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

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 peak
1
players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 05:45 UTC9d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 398 on average152/200+0+0.1%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 335 on average71/200−47−39.9%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 324 on average341/375+100+41.7%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 316 on average96/200+4+4.2%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average13/250+1+9.2%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 271 on average48/100−45−48.3%

Quick answers

from the figures on this page

Rules & Settings

How is MIHA configured in terms of rules and settings?

No gather rate appears in the name of MIHA. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Community is its listing in the server browser. The server has VAC, Valve's anti-cheat, switched on.

Which map is played on MIHA?

MIHA uses a procedural map, which the game generates.

Player Count

What position does MIHA hold in the server rankings?

For the last seven days, MIHA holds rank #15,988 on player hours, in the top 71% of all ranked servers.

How full is MIHA?

At present, MIHA is offline; the last sighting was 9 days 22 hours ago.

Wipe Frequency

What can you expect on wipe day for MIHA?

Recent wipes at this server drew an average peak of 1 players. 1 hours after the latest wipe, the crowd reached its peak.

How often does MIHA wipe?

No rhythm can be told for MIHA yet: too few of its wipes are on record. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. 9 days 23 hours ago the current world was created.

Server Overview

Where can MIHA be found?

There is no region published for MIHA. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 150.251.143.217:28015.

What Rust version is MIHA running?

The build is Rust network protocol 2634 and build 166652 on Windows, running on MIHA. The protocol has to match for you to join, and Steam applies that update.

What is the uptime and reliability of MIHA?

Offline at this moment: MIHA. Last seen 9 days 22 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. First sighting by Rust Analytics: 3 October 2026.

Server Tags

How should you interpret the tags on MIHA?

The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp2 (Max players): Capacity: 2 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set, which MIHA publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.

On Rust Analytics, which lists and filters feature MIHA?

These Rust Analytics lists include MIHA: Rust community servers. 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 2 weeks.

Connection

How can I connect to MIHA?

Type client.connect 150.251.143.217:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Rust's standard survival mode.
mp2
Max players Capacity: 2 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2634
Protocol Your game must run protocol 2634 to connect.
cs166652
Build Game build: 166652.
ptrak
Networking RakNet, the network layer the game ships with.
$r?
Region code No region code has been 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.