RUST METRICSFlight deck · live data
Data live Servers11,668 Players34,317 Populated2,844 Fresh wipes 3 h86 Scan5 min
‹ All servers149.233.174.199:28015
Offline Full Queue Fresh wipe Wipe due No query

Mein Solo Test-Server

Offline 149.233.174.199:28015 checked 30d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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#16,957top 71%
Last wipe30d 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 Oct

Top 71% 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 peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 03:50 UTC30d ago 0 – running 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 timing

What happens on Mein Solo Test-Server when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Mein Solo Test-Server follow?

Its rhythm cannot be told from the wipes of Mein Solo Test-Server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 30 days 23 hours ago the current world was made.

Tag meanings

Which tags does Mein Solo Test-Server carry, and what do they mean?

These are the tags Mein Solo Test-Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Mein Solo Test-Server appear in Rust Metrics lists and filters?

On Rust Metrics, Mein Solo Test-Server 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.

Occupancy

What position does Mein Solo Test-Server hold among Rust servers?

Ranking for Mein Solo Test-Server: #16,957 on seven-day player hours, top 71% of all ranked servers.

How full does Mein Solo Test-Server get?

Mein Solo Test-Server is not responding; status offline, last seen 30 days 23 hours ago.

Server details

Where does Mein Solo Test-Server sit?

No region comes from Mein Solo Test-Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 149.233.174.199:28015.

What Rust version is Mein Solo Test-Server on?

Reading: Mein Solo Test-Server, Rust network protocol 2633 and build 165217, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Mein Solo Test-Server up, and how often does it stay up?

Check: connection. Mein Solo Test-Server is offline at this moment. Last contact was 30 days 23 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 28 September 2026.

Rules and settings

How is Mein Solo Test-Server configured, and what rules are in force?

No gather rate appears in the name: Mein Solo Test-Server. The group cap is 8 players, which is the default in the game. Mode check gives survival; 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 off, Valve's system.

What map is Mein Solo Test-Server on?

Check: map. Procedural, generated by the game, on Mein Solo Test-Server.

Connection

What do you do to join Mein Solo Test-Server?

Press F1 in Rust and enter client.connect 149.233.174.199: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?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.