RUST METRICSFlight deck · live data
Data live Servers11,898 Players102,471 Populated3,963 Fresh wipes 3 h334 Scan5 min
‹ All servers176.49.157.125:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 176.49.157.125:28015 checked 23d 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,777top 61%
Last wipe23d 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
15k10k15k20k2 Oct4 Oct6 Oct9 Oct11 Oct13 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
Tue 6 Oct, 07:34 UTC23d 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?

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. 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 23 days 9 hours ago.

Tag meanings

How should you read the tags on LocalRustServer1337?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from LocalRustServer1337. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does LocalRustServer1337 appear in Rust Metrics lists and filters?

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.

Player count

What position does LocalRustServer1337 hold among Rust servers?

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

How full does LocalRustServer1337 get?

Reading for LocalRustServer1337: offline at this moment; last seen 23 days 6 hours ago.

Server

Which location does LocalRustServer1337 run from?

Reading: location. LocalRustServer1337 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.49.157.125:28015.

What Rust version is LocalRustServer1337 on?

Rust network protocol 2634 and build 166652 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?

LocalRustServer1337 reports offline. The last reading came 23 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 2 October 2026, recorded by Rust Metrics.

Map and rules

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

No gather rate appears in the name: LocalRustServer1337. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. 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?

The game generates a procedural map for LocalRustServer1337.

How to join

How do you connect to LocalRustServer1337?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
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.