RUST METRICSFlight deck · live data
Data live Servers11,790 Players78,914 Populated3,567 Fresh wipes 3 h245 Scan5 min
‹ All servers150.228.63.234:28015
Offline Full Queue Fresh wipe Wipe due No query

MyLocalTest

Offline 150.228.63.234:28015 checked 28d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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#16,557top 70%
Last wipe28d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k29 Sep1 Oct3 Oct4 Oct6 Oct8 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctWed 30 SepTue 29 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 11:41 UTC28d ago 0 – running 1
Wed 30 Sep, 09:00 UTC29d ago 1 – 1.1 days 1
Tue 29 Sep, 18:20 UTC30d ago 1 – 0.6 days 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 timing

What should you expect from wipe day on MyLocalTest?

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

How often does MyLocalTest wipe, and when?

There is no next wipe to predict: MyLocalTest wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 28 days 10 hours ago the current world was made.

Tag meanings

How should you read the tags on MyLocalTest?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166235 (Build): Build 166235; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from MyLocalTest. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does MyLocalTest appear in Rust Metrics lists and filters?

On Rust Metrics, MyLocalTest 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 MyLocalTest hold among Rust servers?

Ranking for MyLocalTest: #16,557 on seven-day player hours, top 70% of all ranked servers.

What player count does MyLocalTest carry?

MyLocalTest is not responding; status offline, last seen 28 days 10 hours ago.

Server

Where does MyLocalTest sit?

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

What Rust version is MyLocalTest on?

Version check: Rust network protocol 2634 and build 166235 on Windows, run by MyLocalTest. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. MyLocalTest last answered 28 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 29 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on MyLocalTest?

No gather rate appears in the name: MyLocalTest. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on MyLocalTest?

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

How to join

How can you get onto MyLocalTest?

Check: join. Open Rust, press F1, then enter client.connect 150.228.63.234:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs166235,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166235
Build Build 166235.
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.