RUST METRICSFlight deck · live data
Data live Servers11,819 Players71,592 Populated3,741 Fresh wipes 3 h132 Scan5 min
‹ All servers178.249.6.69:28015
Offline Full Queue Fresh wipe Wipe due No query

MeinTestServer

Offline 178.249.6.69:28015 checked 2d ago

COM 1 · connect

Server instruments

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

Players now

0% 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#13,101top 59%
Last wipe18d 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
15k10k15k20k24 Oct25 Oct26 Oct27 Oct

Top 59% 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 schedule

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 in play was created 18 days 20 hours ago.

Tag meanings

Which tags does MeinTestServer carry, and what do they mean?

Tags published by MeinTestServer, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 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): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does MeinTestServer appear in Rust Metrics lists and filters?

On Rust Metrics, MeinTestServer sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does MeinTestServer hold among Rust servers?

Player hours over seven days put MeinTestServer at #13,101, in the top 59% of all ranked servers.

What is the population on MeinTestServer?

MeinTestServer is not responding; status offline, last seen 2 days 23 hours ago. Check: players over seven days. Average 1, peak 1.

Server details

What location is MeinTestServer hosted in?

No region tag on MeinTestServer. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 178.249.6.69:28015.

What Rust version is MeinTestServer on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by MeinTestServer. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on MeinTestServer, and is it online?

Reading: offline. MeinTestServer last answered 2 days 23 hours ago. Uptime for the last 2 full days: 0 of 48 hours, or 0%. The first sighting on Rust Metrics was 24 October 2026.

Settings and map

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

Reading the name gives no gather rate for MeinTestServer. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is MeinTestServer on?

Procedural map on MeinTestServer, made by the game's generator.

Join

How do you connect to MeinTestServer?

To join: start Rust, press F1 and type client.connect 178.249.6.69:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players 500 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 Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.