MCR15172
micro
Offline 153.66.237.156:28015 checked 45d ago
Players
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.
-
01COMPlayers 211/250
-
02COMPlayers 125/200
-
03COMPlayers 25/250
-
04COMPlayers 13/250
-
05COMPlayers 25/100
-
06COMPlayers 32/225
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry micro?
These Rust Tracker lists carry micro: Community servers, no tags. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on micro?
The game's server browser reads these tags from micro: gmrust (Game mode): Rust survival, standard mode; mp50 (Max players): Slots: 50; ts8 (Group limit): Team limit is 8, the game default; v2631 (Protocol): Join only if your game is on protocol 2631; cs156658 (Build): This server runs game build 156658; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Schedule
Which wipe times are confirmed for micro?
The record holds too few of micro's wipes to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. 117 days 4 hours since this world was made.
Location and Status
Is micro up, and how does its uptime hold?
Tracking shows micro offline as of now, last seen 45 days 8 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. Rust Tracker logged it first on 13 September 2026.
Which Rust build is micro running?
Rust network protocol 2631 and build 156658 is the build on micro; the platform is Linux. Steam updates it for you; your game must share the protocol to join.
Where does micro sit?
Region: none published by micro. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 153.66.237.156:28015.
Population
How many players are on micro right now?
Last seen 45 days 8 hours ago; micro is offline at present.
Where does micro sit in the server rankings?
Seven-day player hours put micro at #15,172, within the top – of all ranked servers.
Map and Rules
Which settings and rules are confirmed on micro?
The name of micro carries no gather rate. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. Listed under Community in the server browser, it is a community server. On: VAC, Valve's anti-cheat.
Which map is confirmed for micro?
Procedural map on micro, made by the game.
Connect
What is the way to join micro?
Open the console in Rust with F1 after starting the game, then type client.connect 153.66.237.156:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2631,gmrust,cs156658,ts8
Game
gmrust
mp50
ts8
v2631
cs156658
ptrak
$r?
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.