RUST METRICSFlight deck · live data
Data live Servers11,737 Players72,806 Populated3,664 Fresh wipes 3 h126 Scan5 min
‹ All servers191.82.202.248:28015
Offline Full Queue Fresh wipe Wipe due No query

Mi Servidor Solo

Offline 191.82.202.248:28015 checked 15d 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#13,277top 61%
Last wipe16d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 06:29 UTC16d ago 1 – running 0

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 schedule

What happens on Mi Servidor Solo when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does Mi Servidor Solo wipe, and when?

The rhythm of Mi Servidor Solo'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. 16 days 6 hours ago the current world was made.

Lists and filters

Which tags does Mi Servidor Solo carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): The server runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from Mi Servidor Solo. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

These Rust Metrics lists carry Mi Servidor Solo: 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.

Occupancy

Where does Mi Servidor Solo sit in the rankings?

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

What is the population on Mi Servidor Solo?

Mi Servidor Solo is not responding; status offline, last seen 15 days 13 hours ago.

Operator and location

Where does Mi Servidor Solo sit?

No region tag on Mi Servidor Solo. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 191.82.202.248:28015.

What Rust version is Mi Servidor Solo on?

Rust network protocol 2634 and build 167398 on Windows is the build Mi Servidor Solo runs. Check: protocol. To join, your game must match; Steam handles the update.

Is Mi Servidor Solo up, and how often does it stay up?

Check: connection. Mi Servidor Solo is offline at this moment. Last contact was 15 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 12 October 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for Mi Servidor Solo. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on Mi Servidor Solo?

The game generates a procedural map for Mi Servidor Solo.

How to join

How do you connect to Mi Servidor Solo?

Press F1 in Rust and enter client.connect 191.82.202.248:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build The server runs game build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.