MiServidorSolo
Offline 84.127.130.24:28015 checked 40d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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- 229/250
- 131/225
- 20/250
- 18/250
- 20/100
- 68/200
Quick answers
from the figures on this pageWipe timing
How often does MiServidorSolo wipe, and when?
Its rhythm cannot be told from the wipes of MiServidorSolo 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 it runs now was made 41 days 1 hours ago.
Tag meanings
How should you read the tags on MiServidorSolo?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): Slots: 2; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from MiServidorSolo. 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 MiServidorSolo?
These Rust Metrics lists carry MiServidorSolo: 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.
Player count
Where does MiServidorSolo sit in the rankings?
Ranking for MiServidorSolo: #13,305 on seven-day player hours, top – of all ranked servers.
How full does MiServidorSolo get?
Status for MiServidorSolo: offline. Last seen 40 days 7 hours ago.
Operator and location
Where does MiServidorSolo sit?
No region tag on MiServidorSolo. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 84.127.130.24:28015.
What Rust version is MiServidorSolo on?
Reading: MiServidorSolo, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is MiServidorSolo up, and how often does it stay up?
MiServidorSolo reports offline. The last reading came 40 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 18 September 2026.
Map and rules
What settings and rules apply on MiServidorSolo?
Check: gather rate. The name MiServidorSolo 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. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is MiServidorSolo on?
The game generates a procedural map for MiServidorSolo.
How to join
How can you get onto MiServidorSolo?
To join: start Rust, press F1 and type client.connect 84.127.130.24:28015. Or press Launch Rust here and Steam opens the game and connects you.