RUST METRICSFlight deck · live data
Data live Servers11,649 Players43,286 Populated3,030 Fresh wipes 3 h94 Scan5 min
‹ All servers213.135.155.237:28015
Offline Full Queue Fresh wipe Wipe due No query

My Local Server

Offline 213.135.155.237:28015 checked 5d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /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 average0peak 1
Rank#13,018top 58%
Last wipe5d 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
15k10k15k20k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

Top 58% 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
Fri 23 Oct, 18:43 UTC5d 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 should you expect from wipe day on My Local Server?

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

What wipe timing does My Local Server follow?

To tell the rhythm of My Local Server, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 5 days 13 hours ago.

Tags

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from My Local Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show My Local Server?

Rust Metrics lists featuring My Local Server: 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; Last wipe: In the last week.

Population

What position does My Local Server hold among Rust servers?

Player hours over seven days put My Local Server at #13,018, in the top 58% of all ranked servers.

What is the population on My Local Server?

My Local Server is not responding; status offline, last seen 5 days 7 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Server

Where does My Local Server sit?

No region comes from My Local Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 213.135.155.237:28015.

What Rust version is My Local Server on?

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

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

My Local Server reports offline. The last reading came 5 days 7 hours ago. Uptime for the last 5 full days: 2 of 120 hours, or 2%. Reading: first seen 23 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on My Local Server?

No gather rate appears in the name: My Local Server. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.

What map is My Local Server on?

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

Join

How can you get onto My Local Server?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players Slots: 500.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.