Rust Server TrendsSeismic network · station log
Recording Stations11,634 Players45,438 Active3,128 Wipes · 3 h94 48 h

Station XX-14662 · no signal

MiServidorSoloTest

Offline 138.84.41.111:28015 checked 11d ago

Connect
Players now
0/ 2
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,662
top 67%
Last wipe
12d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14662 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 2 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 peak
1players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 02:34 UTC12d ago M0.0steady 1 – running 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 536 on average
436/ 475
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
209/ 225
Rustoria.co - EU Main EU · groups of 16+ · weekly · 318 on average
25/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 317 on average
27/ 250
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 276 on average
136/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average
43/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on MiServidorSoloTest?

A procedural map runs on MiServidorSoloTest, generated by the game.

Which settings and rules apply on MiServidorSoloTest?

The name of MiServidorSoloTest gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on MiServidorSoloTest?

MiServidorSoloTest is not responding at this moment and is offline, last seen 11 days 1 hours ago.

How does MiServidorSoloTest rank against other Rust servers?

The last seven days of player hours place MiServidorSoloTest at #14,662, in the top 67% of all ranked servers.

Server details

How reliably does MiServidorSoloTest stay online?

No contact with MiServidorSoloTest right now, and the last recorded contact was 11 days 1 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 15 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does MiServidorSoloTest run from?

A region is not published by MiServidorSoloTest. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 138.84.41.111:28015 is the address it uses.

What build of Rust does MiServidorSoloTest use?

Rust network protocol 2634 and build 167781 on Windows is what MiServidorSoloTest runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on MiServidorSoloTest?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 1 hours after the wipe.

On what timetable does MiServidorSoloTest run its wipes?

The rhythm of MiServidorSoloTest cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 12 days 5 hours.

Server tags

What do the server tags on MiServidorSoloTest mean?

These are the tags MiServidorSoloTest publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp2 (Max players): 2 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does MiServidorSoloTest appear?

The Rust Server Trends lists that take in MiServidorSoloTest are: Rust community servers without the side modes. 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; Last wipe: In the last 2 weeks.

Connecting

How do you connect to MiServidorSoloTest?

To join, enter client.connect 138.84.41.111:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp2
Max players 2 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build The game build is 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.