RUST METRICSFlight deck · live data
Data live Servers11,670 Players57,098 Populated3,402 Fresh wipes 3 h100 Scan5 min
‹ All servers79.155.128.255:28015
Offline Full Queue Fresh wipe Wipe due No query

Mi servidor privado

Offline 79.155.128.255:28015 checked 19d 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,637top 62%
Last wipe19d 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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

Top 62% 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 privado follow?

The rhythm of Mi servidor privado'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. The world it runs now was made 19 days 15 hours ago.

Tag meanings

How should you read the tags on Mi servidor privado?

These are the tags Mi servidor privado publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Game build reading: 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Mi servidor privado?

These Rust Metrics lists carry Mi servidor privado: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does Mi servidor privado hold among Rust servers?

Ranking for Mi servidor privado: #13,637 on seven-day player hours, top 62% of all ranked servers.

How full does Mi servidor privado get?

Status for Mi servidor privado: offline. Last seen 19 days 9 hours ago.

Server details

What location is Mi servidor privado hosted in?

Reading: location. Mi servidor privado gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 79.155.128.255:28015.

What Rust version is Mi servidor privado on?

Rust network protocol 2634 and build 167231 on Windows is the build Mi servidor privado runs. Matching protocol is required to join. Let Steam update your game.

Is Mi servidor privado up, and how often does it stay up?

Check: connection. Mi servidor privado is offline at this moment. Last contact was 19 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 8 October 2026, recorded by Rust Metrics.

Map and rules

How is Mi servidor privado configured, and what rules are in force?

Reading the name gives no gather rate for Mi servidor privado. The group cap is 8 players, which is the default in the game. 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. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is Mi servidor privado on?

The game generates a procedural map for Mi servidor privado.

Join

What do you do to join Mi servidor privado?

Press F1 in Rust and enter client.connect 79.155.128.255: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,cs167231,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build Game build reading: 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.