RUST METRICSFlight deck · live data
Data live Servers11,786 Players66,925 Populated3,511 Fresh wipes 3 h190 Scan5 min
‹ All servers114.199.47.250:28015
Offline Full Queue Fresh wipe Wipe due No query

My Local Rust

Offline 114.199.47.250:28015 checked 12d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 3 /5

Players now

60% 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#10,550top 49%
Last wipe12d 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
15k10k15k20k10 Oct13 Oct16 Oct18 Oct21 Oct24 Oct

Top 49% 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 peak3players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 14:59 UTC12d ago 3 – running 1

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 should you expect from wipe day on My Local Rust?

At their busiest, its recent wipes drew 3 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does My Local Rust follow?

The rhythm of My Local Rust's wipes cannot be told yet: too few 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 12 days 21 hours ago.

Tag meanings

How should you read the tags on My Local Rust?

Tags published by My Local Rust, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does My Local Rust appear in Rust Metrics lists and filters?

These Rust Metrics lists carry My Local Rust: 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; Last wipe: In the last 2 weeks.

Player count

What position does My Local Rust hold among Rust servers?

Ranking for My Local Rust: #10,550 on seven-day player hours, top 49% of all ranked servers.

How full does My Local Rust get?

Reading for My Local Rust: offline at this moment; last seen 12 days 1 hours ago.

Server details

What location is My Local Rust hosted in?

No region tag on My Local Rust. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 114.199.47.250:28015.

What Rust version is My Local Rust on?

Reading: My Local Rust, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. My Local Rust last answered 12 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 10 October 2026.

Map and rules

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

Reading the name gives no gather rate for My Local Rust. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is My Local Rust on?

Check: map. Procedural, generated by the game, on My Local Rust.

Join

What do you do to join My Local Rust?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.