RUST METRICSFlight deck · live data
Data live Servers11,761 Players76,398 Populated3,723 Fresh wipes 3 h136 Scan5 min
‹ All servers136.33.51.113:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Test

Offline 136.33.51.113:28015 checked 26d 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 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#13,967top 59%
Last wipe26d 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 14:34 UTC26d 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 timing

What happens on Local Test when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Local Test follow?

Its rhythm cannot be told from the wipes of Local Test 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. 26 days 23 hours ago the current world was made.

Lists and filters

How should you read the tags on Local Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from Local Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Local Test?

These Rust Metrics lists carry Local Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does Local Test sit in the rankings?

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

How full does Local Test get?

Reading for Local Test: offline at this moment; last seen 26 days 20 hours ago.

Server details

What location is Local Test hosted in?

No region comes from Local Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 136.33.51.113:28015.

What Rust version is Local Test on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by Local Test. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Local Test, and is it online?

Check: connection. Local Test is offline at this moment. Last contact was 26 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 1 October 2026.

Rules and settings

How is Local Test configured, and what rules are in force?

Check: gather rate. The name Local Test does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How can you get onto Local Test?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players The server holds 500 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
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.