RUST METRICSFlight deck · live data
Data live Servers11,615 Players36,329 Populated2,867 Fresh wipes 3 h53 Scan5 min
‹ All servers92.46.82.7:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 92.46.82.7:28015 checked 32d ago

COM 1 · connect

Server instruments

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

Players now

10% 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,896top 61%
Last wipe32d 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
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 Oct

Top 61% 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
Fri 25 Sep, 11:28 UTC32d 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 happens on LocalRustServer1337 when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

When does LocalRustServer1337 wipe?

The rhythm of LocalRustServer1337'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. 32 days 16 hours ago the current world was made.

Lists and filters

Which tags does LocalRustServer1337 carry, and what do they mean?

Tags published by LocalRustServer1337, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does LocalRustServer1337 appear in Rust Metrics lists and filters?

On Rust Metrics, LocalRustServer1337 sits in these lists: 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.

Player count

What position does LocalRustServer1337 hold among Rust servers?

Ranking for LocalRustServer1337: #13,896 on seven-day player hours, top 61% of all ranked servers.

What player count does LocalRustServer1337 carry?

Reading for LocalRustServer1337: offline at this moment; last seen 32 days 15 hours ago.

Server

What location is LocalRustServer1337 hosted in?

No region tag on LocalRustServer1337. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 92.46.82.7:28015.

What Rust version is LocalRustServer1337 on?

Rust network protocol 2633 and build 165217 on Windows is the build LocalRustServer1337 runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on LocalRustServer1337, and is it online?

Check: connection. LocalRustServer1337 is offline at this moment. Last contact was 32 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 25 September 2026, recorded by Rust Metrics.

Settings and map

How is LocalRustServer1337 configured, and what rules are in force?

Reading the name gives no gather rate for LocalRustServer1337. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.

What map is LocalRustServer1337 on?

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

How to join

How can you get onto LocalRustServer1337?

To join: start Rust, press F1 and type client.connect 92.46.82.7:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.