RUST METRICSFlight deck · live data
Data live Servers11,883 Players104,335 Populated3,951 Fresh wipes 3 h530 Scan5 min
‹ All servers146.120.227.195:28015
Offline Full Queue Fresh wipe Wipe due No query

My Test Server

Offline 146.120.227.195:28015 checked 9d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#14,264top 65%
Last wipe9d 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
15k10k15k20k2 Oct5 Oct8 Oct21 Oct24 Oct27 Oct

Top 65% 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 14:32 UTC9d ago 1 – 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 schedule

What happens on My Test Server when wipe day comes?

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

What wipe timing does My Test Server follow?

The rhythm of My Test Server's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 9 days 4 hours ago the current world was made.

Tag meanings

Which tags does My Test Server carry, and what do they mean?

Tags published by My Test Server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; 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 My Test Server?

On Rust Metrics, My Test Server 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; Last wipe: In the last 2 weeks.

Population

Where does My Test Server sit in the rankings?

Ranking for My Test Server: #14,264 on seven-day player hours, top 65% of all ranked servers.

What is the population on My Test Server?

Reading for My Test Server: offline at this moment; last seen 9 days 3 hours ago.

Server

Which location does My Test Server run from?

No region comes from My Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 146.120.227.195:28015.

What Rust version is My Test Server on?

Rust network protocol 2634 and build 167781 on Windows is the build My Test Server runs. Matching protocol is required to join. Let Steam update your game.

Is My Test Server up, and how often does it stay up?

Reading: offline. My Test Server last answered 9 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 2 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on My Test Server?

Check: gather rate. The name My Test Server does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — 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.

Which map is live on My Test Server?

The game generates a procedural map for My Test Server.

How to join

How can you get onto My Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
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.