RUST METRICSFlight deck · live data
Data live Servers11,643 Players37,948 Populated2,905 Fresh wipes 3 h67 Scan5 min
‹ All servers65.185.1.227:28015
Offline Full Queue Fresh wipe Wipe due No query

Mi Servidor Solo

Offline 65.185.1.227:28015 checked 32d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,087top 61%
Last wipe32d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What wipe timing does Mi Servidor Solo follow?

Its rhythm cannot be told from the wipes of Mi Servidor Solo on record: there are too few. 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 32 days 8 hours ago.

Tags

How should you read the tags on Mi Servidor Solo?

These are the tags Mi Servidor Solo publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $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.

Where does Mi Servidor Solo appear in Rust Metrics lists and filters?

On Rust Metrics, Mi Servidor Solo sits in these lists: 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

What position does Mi Servidor Solo hold among Rust servers?

Ranking for Mi Servidor Solo: #14,087 on seven-day player hours, top 61% of all ranked servers.

How full does Mi Servidor Solo get?

Reading for Mi Servidor Solo: offline at this moment; last seen 32 days 5 hours ago.

Operator and location

Which location does Mi Servidor Solo run from?

No region tag on Mi Servidor Solo. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 65.185.1.227:28015.

What Rust version is Mi Servidor Solo on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by Mi Servidor Solo. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Mi Servidor Solo, and is it online?

Check: connection. Mi Servidor Solo is offline at this moment. Last contact was 32 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 25 September 2026.

Settings and map

What rules does Mi Servidor Solo enforce, and what are its settings?

No gather rate appears in the name: Mi Servidor Solo. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is Mi Servidor Solo on?

Check: map. Procedural, generated by the game, on Mi Servidor Solo.

How to join

What do you do to join Mi Servidor Solo?

Check: join. Open Rust, press F1, then enter client.connect 65.185.1.227:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.