RUST METRICSFlight deck · live data
Data live Servers11,696 Players45,884 Populated3,156 Fresh wipes 3 h101 Scan5 min
‹ All servers1.165.94.220:28015
Offline Full Queue Fresh wipe Wipe due No query

MyTestServer

Offline 1.165.94.220:28015 checked 7d 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,159top 59%
Last wipe7d 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
15k10k15k20k21 Oct22 Oct24 Oct25 Oct27 Oct28 Oct

Top 59% 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
Wed 21 Oct, 13:47 UTC7d 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

Reset cycle

What happens on MyTestServer when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

When does MyTestServer wipe?

To tell the rhythm of MyTestServer, too few of its wipes are on record. 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 7 days 10 hours ago.

Tag meanings

How should you read the tags on MyTestServer?

Tags published by MyTestServer, 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): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does MyTestServer appear in Rust Metrics lists and filters?

Rust Metrics lists featuring MyTestServer: 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; Last wipe: In the last 2 weeks.

Player count

What position does MyTestServer hold among Rust servers?

Ranking for MyTestServer: #13,159 on seven-day player hours, top 59% of all ranked servers.

What player count does MyTestServer carry?

Reading for MyTestServer: offline at this moment; last seen 7 days 10 hours ago. Check: players over seven days. Average 1, peak 1.

Operator and location

What location is MyTestServer hosted in?

Reading: location. MyTestServer gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 1.165.94.220:28015.

What Rust version is MyTestServer on?

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

Is MyTestServer up, and how often does it stay up?

Reading: offline. MyTestServer last answered 7 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 21 October 2026.

Rules and settings

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

No gather rate appears in the name: MyTestServer. No limit is set beyond the default. Groups take up to 8 players. 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. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on MyTestServer?

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

Join

How can you get onto MyTestServer?

Press F1 in Rust and enter client.connect 1.165.94.220: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 The game mode is plain Rust survival.
mp500
Max players 500 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.