RUST METRICSFlight deck · live data
Data live Servers11,722 Players56,412 Populated3,390 Fresh wipes 3 h140 Scan5 min
‹ All servers95.32.2.111:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 95.32.2.111:28015 checked 24d ago

COM 1 · connect

Server instruments

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

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#15,967top 70%
Last wipe24d 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 Oct3 Oct5 Oct6 Oct8 Oct10 Oct

Top 70% 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.

usual gap1.2 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sat 3 OctFri 2 Oct
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
Sat 3 Oct, 05:53 UTC24d ago 0 – running 0
Fri 2 Oct, 00:28 UTC25d ago 1 – 1.2 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 LocalRustServer1337?

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

How often does LocalRustServer1337 wipe, and when?

To tell the rhythm of LocalRustServer1337, 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 it runs now was made 24 days 17 hours ago.

Tags

How should you read the tags on LocalRustServer1337?

These are the tags LocalRustServer1337 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): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Game build reading: 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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 LocalRustServer1337?

Rust Metrics lists featuring LocalRustServer1337: 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

What position does LocalRustServer1337 hold among Rust servers?

Player hours over seven days put LocalRustServer1337 at #15,967, in the top 70% of all ranked servers.

What is the population on LocalRustServer1337?

Reading for LocalRustServer1337: offline at this moment; last seen 24 days 17 hours ago.

Server details

Where does LocalRustServer1337 sit?

Reading: location. LocalRustServer1337 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 95.32.2.111:28015.

What Rust version is LocalRustServer1337 on?

Reading: LocalRustServer1337, Rust network protocol 2634 and build 166652, Windows. Matching protocol is required to join. Let Steam update your game.

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

LocalRustServer1337 reports offline. The last reading came 24 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 30 September 2026.

Map and rules

What rules does LocalRustServer1337 enforce, and what are its settings?

Check: gather rate. The name LocalRustServer1337 does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on LocalRustServer1337?

Procedural map on LocalRustServer1337, made by the game's generator.

Join

How do you connect to LocalRustServer1337?

Press F1 in Rust and enter client.connect 95.32.2.111:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Game build reading: 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.