RUST METRICSFlight deck · live data
Data live Servers11,611 Players33,784 Populated2,810 Fresh wipes 3 h69 Scan5 min
‹ All servers73.53.52.225:28015
Offline Full Queue Fresh wipe Wipe due No query

My Local Test Server

Offline 73.53.52.225:28015 checked 30d ago

COM 1 · connect
Launch Rust and join

Server instruments

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

Players now

10% 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,563top 61%
Last wipe38d 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
15k10k15k20k20 Sep23 Sep26 Sep29 Sep2 Oct5 Oct

Top 61% 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
Sun 20 Sep, 14:12 UTC38d 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 My Local Test Server when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

When does My Local Test Server wipe?

To tell the rhythm of My Local Test Server, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 38 days 16 hours ago the current world was made.

Tags

How should you read the tags on My Local Test Server?

These are the tags My Local Test Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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 My Local Test Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry My Local Test Server: 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.

Population

Where does My Local Test Server sit in the rankings?

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

What player count does My Local Test Server carry?

Reading for My Local Test Server: offline at this moment; last seen 30 days 12 hours ago.

Operator and location

Where does My Local Test Server sit?

No region tag on My Local Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 73.53.52.225:28015.

What Rust version is My Local Test Server on?

Rust network protocol 2633 and build 163794 on Windows is the build My Local Test Server runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is My Local Test Server, and is it online now?

Check: connection. My Local Test Server is offline at this moment. Last contact was 30 days 12 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 15 September 2026.

Settings and map

What rules does My Local Test Server enforce, and what are its settings?

No gather rate appears in the name: My Local Test Server. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is My Local Test Server on?

Procedural map on My Local Test Server, made by the game's generator.

How to join

How can you get onto My Local Test Server?

To join: start Rust, press F1 and type client.connect 73.53.52.225: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?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build The server runs game build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.