RUST METRICSFlight deck · live data
Data live Servers11,615 Players40,773 Populated3,012 Fresh wipes 3 h86 Scan5 min
‹ All servers90.154.71.212:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 90.154.71.212:28015 checked 39d 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,259no region published
Last wipe39d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
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 18 Sep, 15:49 UTC39d ago 1 – 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

Wipe schedule

What should you expect from wipe day on LocalRustServer1337?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does LocalRustServer1337 follow?

To tell the rhythm of LocalRustServer1337, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 39 days 15 hours ago.

Tag meanings

How should you read the tags on LocalRustServer1337?

Tags published by LocalRustServer1337, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs162929 (Build): The server runs game build 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show LocalRustServer1337?

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

Player count

What position does LocalRustServer1337 hold among Rust servers?

Player hours over seven days put LocalRustServer1337 at #13,259, in the top – of all ranked servers.

What player count does LocalRustServer1337 carry?

Status for LocalRustServer1337: offline. Last seen 39 days 15 hours ago.

Server details

Which location does LocalRustServer1337 run from?

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 90.154.71.212:28015.

What Rust version is LocalRustServer1337 on?

Reading: LocalRustServer1337, Rust network protocol 2633 and build 162929, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

LocalRustServer1337 reports offline. The last reading came 39 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 17 September 2026.

Map and rules

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

Reading the name gives no gather rate for LocalRustServer1337. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is off. That is Valve's anti-cheat.

Which map is live on LocalRustServer1337?

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

Join

What do you do to join LocalRustServer1337?

Press F1 in Rust and enter client.connect 90.154.71.212: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?,v2633,gmrust,cs162929,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs162929
Build The server runs game build 162929.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.