RUST METRICSFlight deck · live data
Data live Servers11,758 Players58,600 Populated3,466 Fresh wipes 3 h133 Scan5 min
‹ All servers138.84.41.111:28015
Offline Full Queue Fresh wipe Wipe due No query

MiServidorSoloTest

Offline 138.84.41.111:28015 checked 11d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

Players now

0% 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,662top 67%
Last wipe12d 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
15k10k15k20k16 Oct18 Oct19 Oct21 Oct22 Oct24 Oct

Top 67% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 02:34 UTC12d ago 1 – running 1

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

Reset cycle

What happens on MiServidorSoloTest 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 1 hours.

What wipe timing does MiServidorSoloTest follow?

To tell the rhythm of MiServidorSoloTest, too few of its wipes are on record. 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 in play was created 12 days 19 hours ago.

Tags

Which tags does MiServidorSoloTest carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): Slots: 2; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from MiServidorSoloTest. 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 MiServidorSoloTest?

Rust Metrics lists featuring MiServidorSoloTest: 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; Last wipe: In the last 2 weeks.

Occupancy

What position does MiServidorSoloTest hold among Rust servers?

Ranking for MiServidorSoloTest: #14,662 on seven-day player hours, top 67% of all ranked servers.

What player count does MiServidorSoloTest carry?

Status for MiServidorSoloTest: offline. Last seen 11 days 16 hours ago.

Server details

What location is MiServidorSoloTest hosted in?

Reading: location. MiServidorSoloTest gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 138.84.41.111:28015.

What Rust version is MiServidorSoloTest on?

Reading: MiServidorSoloTest, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

Is MiServidorSoloTest up, and how often does it stay up?

Check: connection. MiServidorSoloTest is offline at this moment. Last contact was 11 days 16 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 15 October 2026.

Map and rules

What rules does MiServidorSoloTest enforce, and what are its settings?

Reading the name gives no gather rate for MiServidorSoloTest. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on MiServidorSoloTest?

Check: map. Procedural, generated by the game, on MiServidorSoloTest.

How to join

How can you get onto MiServidorSoloTest?

Press F1 in Rust and enter client.connect 138.84.41.111: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 mp2,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players Slots: 2.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
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.