RUST METRICSFlight deck · live data
Data live Servers11,640 Players32,367 Populated2,784 Fresh wipes 3 h73 Scan5 min
‹ All servers104.28.200.204:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 104.28.200.204:28015 checked 16d 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,307top 61%
Last wipe18d agono schedule published
Next wipe–no wipe 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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does LocalRustServer1337 follow?

Its rhythm cannot be told from the wipes of LocalRustServer1337 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. The world in play was created 18 days 11 hours ago.

Tag meanings

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

These are the tags LocalRustServer1337 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. 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 LocalRustServer1337?

These Rust Metrics lists carry LocalRustServer1337: 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.

Population

Where does LocalRustServer1337 sit in the rankings?

Player hours over seven days put LocalRustServer1337 at #13,307, in the top 61% of all ranked servers.

How full does LocalRustServer1337 get?

Status for LocalRustServer1337: offline. Last seen 16 days 10 hours ago.

Server details

What location is LocalRustServer1337 hosted in?

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

What Rust version is LocalRustServer1337 on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by LocalRustServer1337. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. LocalRustServer1337 last answered 16 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 12 October 2026.

Rules and settings

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

No gather rate appears in the name: LocalRustServer1337. 8 players per group, the default value. Mode check gives survival; 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.

Which map is live on LocalRustServer1337?

The game generates a procedural map for LocalRustServer1337.

Connection

How can you get onto LocalRustServer1337?

Press F1 in Rust and enter client.connect 104.28.200.204: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,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.