MIKE
Offline 176.50.140.24:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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- 237/275
- 162/200
- 28/250
- 16/250
- 34/100
- 45/200
Quick answers
from the figures on this pageReset cycle
How often does MIKE wipe, and when?
The rhythm of MIKE's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 48 days 12 hours ago.
Tag meanings
How should you read the tags on MIKE?
These are the tags MIKE publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; 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 MIKE?
These Rust Metrics lists carry MIKE: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does MIKE sit in the rankings?
Player hours over seven days put MIKE at #15,126, in the top – of all ranked servers.
What is the population on MIKE?
MIKE is not responding; status offline, last seen 44 days 23 hours ago.
Operator and location
Where does MIKE sit?
Reading: location. MIKE gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 176.50.140.24:28015.
What Rust version is MIKE on?
Version check: Rust network protocol 2633 and build 163794 on Windows, run by MIKE. Matching protocol is required to join. Let Steam update your game.
How reliable is MIKE, and is it online now?
Reading: offline. MIKE last answered 44 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on MIKE?
Check: gather rate. The name MIKE does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
Which map is live on MIKE?
Procedural map on MIKE, made by the game's generator.
Connection
What do you do to join MIKE?
Press F1 in Rust and enter client.connect 176.50.140.24:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.