RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h82 Scan5 min
‹ All servers176.116.167.6:28015
Offline Full Queue Fresh wipe Wipe due No query

My Solo 3000 World

Offline 176.116.167.6:28015 checked 18d 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,595top 62%
Last wipe25d 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
15k10k15k20k20 Sep25 Sep1 Oct6 Oct12 Oct17 Oct

Top 62% 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
Sat 3 Oct, 05:13 UTC25d 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

Wipe timing

What should you expect from wipe day on My Solo 3000 World?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

What wipe timing does My Solo 3000 World follow?

Its rhythm cannot be told from the wipes of My Solo 3000 World on record: there are too few. 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 25 days 11 hours ago.

Lists and filters

How should you read the tags on My Solo 3000 World?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from My Solo 3000 World. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does My Solo 3000 World appear in Rust Metrics lists and filters?

On Rust Metrics, My Solo 3000 World sits in these lists: 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.

Population

Where does My Solo 3000 World sit in the rankings?

Player hours over seven days put My Solo 3000 World at #13,595, in the top 62% of all ranked servers.

What is the population on My Solo 3000 World?

My Solo 3000 World is not responding; status offline, last seen 18 days 9 hours ago.

Server details

Where does My Solo 3000 World sit?

Reading: location. My Solo 3000 World gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.116.167.6:28015.

What Rust version is My Solo 3000 World on?

Reading: My Solo 3000 World, Rust network protocol 2634 and build 166652, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is My Solo 3000 World up, and how often does it stay up?

Check: connection. My Solo 3000 World is offline at this moment. Last contact was 18 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 September 2026.

Rules and settings

How is My Solo 3000 World configured, and what rules are in force?

No gather rate appears in the name: My Solo 3000 World. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. 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 My Solo 3000 World on?

Check: map. Procedural, generated by the game, on My Solo 3000 World.

How to join

How can you get onto My Solo 3000 World?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
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.