RUST METRICSFlight deck · live data
Data live Servers11,809 Players80,805 Populated3,802 Fresh wipes 3 h104 Scan5 min
‹ All servers80.142.4.172:28015
Offline Full Queue Fresh wipe Wipe due No query

MeinTestServer

Offline 80.142.4.172:28015 checked 8d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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#15,353top 70%
Last wipe11d agono schedule published
Next wipe–no wipe 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 Oct20 Oct23 Oct25 Oct27 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does MeinTestServer follow?

Its rhythm cannot be told from the wipes of MeinTestServer 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 it runs now was made 11 days 23 hours ago.

Tags

How should you read the tags on MeinTestServer?

These are the tags MeinTestServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does MeinTestServer appear in Rust Metrics lists and filters?

On Rust Metrics, MeinTestServer sits in these lists: Rust community servers: live readings. 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.

Population

What position does MeinTestServer hold among Rust servers?

Ranking for MeinTestServer: #15,353 on seven-day player hours, top 70% of all ranked servers.

What player count does MeinTestServer carry?

Status for MeinTestServer: offline. Last seen 8 days 13 hours ago.

Operator and location

Which location does MeinTestServer run from?

Reading: location. MeinTestServer gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 80.142.4.172:28015.

What Rust version is MeinTestServer on?

Rust network protocol 2634 and build 167781 on Windows is the build MeinTestServer runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is MeinTestServer, and is it online now?

Check: connection. MeinTestServer is offline at this moment. Last contact was 8 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 16 October 2026.

Rules and settings

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

Check: gather rate. The name MeinTestServer does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is MeinTestServer on?

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

Connection

What do you do to join MeinTestServer?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players Slots: 500.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.