micro
Offline 153.66.239.214: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
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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.
Quick answers
From the figures on this page.
Map and rules
Where can you read the rules and settings that apply on micro?
No gather rate appears in the name micro. The default group limit of 8 players applies. Filed under survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. Filed under Community in the server browser, it is a community server. VAC is on: Valve's anti-cheat is enabled.
Which map is in use on micro?
Generated by the game, the map is procedural on micro.
Lists and filters
On Rust Server Index, which lists and filters carry micro?
These lists on Rust Server Index take micro: Community Rust servers, indexed. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which tags are attached to micro, and what do they stand for?
The server's own tags are listed here, and the game's server browser reads them: micro gives gmrust (Game mode): Rust survival, as standard; mp50 (Max players): The queue ceiling sits at 50; ts8 (Group limit): Game default applies: teams of up to 8; v2631 (Protocol): Your client must run protocol 2631 to connect; cs156658 (Build): It runs build 156658; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
How often is micro wiped, and on what schedule?
micro's rhythm cannot be told yet: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 117 days 1 hours is when its current world was made.
Players and ranking
Is micro quiet or crowded?
Filed under offline: micro, last seen 45 days 15 hours ago.
Operator and status
Which Rust build is micro running?
Rust network protocol 2631 and build 156658, on Linux, is what micro runs. The protocol must match before you can join, and Steam takes care of updating it.
Is micro reachable, and does it stay up?
The server is down at this moment; the last sighting of micro was 45 days 15 hours ago. Uptime for the last 7 full days came to 0%, 0 hours out of 168. On 13 September 2026 it was first seen by Rust Server Index.
Where in the world is micro hosted?
No region is published by micro. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 153.66.239.214:28015.
Connecting
How can you connect to micro?
If you would rather use the console, press F1 in Rust and enter client.connect 153.66.239.214:28015. You can also choose Launch Rust and join here; that opens Rust through 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.