RUST METRICSFlight deck · live data
Data live Servers11,720 Players60,549 Populated3,378 Fresh wipes 3 h181 Scan5 min
‹ All servers106.72.130.224:28015
Offline Full Queue Fresh wipe Wipe due No query

MySoloServer

Offline 106.72.130.224:28015 checked 21h 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 avg7-day peak
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 average1peak 1
Rank#5,212top 23%
Last wipe4d agono schedule published
Next wipe–no rhythm it keeps
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75113:0015:0016:0018:0019:0013:00

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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap5.8 daysbetween real wipes
on rhythm43%of its recent wipes
wipe-day peak1players, last three wipes
crowd held75%else halves by day 2

The first 48 hours of its last wipes

Sat 24 OctSat 24 OctMon 19 Oct
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
Sat 24 Oct, 20:07 UTC4d ago 1 – running 1
Sat 24 Oct, 11:04 UTC5d ago 1 – 0.4 days 0
Mon 19 Oct, 07:12 UTC10d ago 1 held half 5.2 days 1
Tue 13 Oct, 12:47 UTC15d ago 1 held half 5.8 days 1
Sun 4 Oct, 01:39 UTC25d ago 1 held half 9.5 days 1
Wed 23 Sep, 12:45 UTC35d ago 1 halved by day 2 10.5 days 1
Sun 20 Sep, 10:54 UTC39d ago 1 held half 3.1 days 0
Mon 14 Sep, 00:17 UTC45d ago 1 halved by day 2 6.4 days 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 MySoloServer when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 75% of its recent wipes. When it didn't hold, by day 2 it fell below half.

When does MySoloServer wipe?

There is no next wipe to predict: MySoloServer wipes at irregular times. 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 4 days 15 hours ago.

Lists and filters

How should you read the tags on MySoloServer?

These are the tags MySoloServer publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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 MySoloServer?

Rust Metrics lists featuring MySoloServer: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Population

What position does MySoloServer hold among Rust servers?

Ranking for MySoloServer: #5,212 on seven-day player hours, top 23% of all ranked servers.

What is the population on MySoloServer?

Status for MySoloServer: offline. Last seen 21 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Check: 48-hour peak. 15:00 UTC, 1 players on average.

Server

Which location does MySoloServer run from?

No region comes from MySoloServer. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 106.72.130.224:28015.

What Rust version is MySoloServer on?

Reading: MySoloServer, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is MySoloServer, and is it online now?

Reading: offline. MySoloServer last answered 21 hours ago. Uptime for the last 7 full days: 50 of 168 hours, or 30%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

How is MySoloServer configured, and what rules are in force?

Reading the name gives no gather rate for MySoloServer. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is MySoloServer on?

The game generates a procedural map for MySoloServer.

How to join

How can you get onto MySoloServer?

Press F1 in Rust and enter client.connect 106.72.130.224: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
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.