RUST METRICSFlight deck · live data
Data live Servers11,739 Players51,557 Populated3,316 Fresh wipes 3 h122 Scan5 min
‹ All servers141.98.87.118:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 141.98.87.118:28015 checked 32d 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,303top 65%
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
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 Oct

Top 65% 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 peak3players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 26 Sep, 18:52 UTC32d ago 3 – 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 happens on LocalRustServer1337 when wipe day comes?

The busiest point of its recent wipes drew 3 players on average. After the latest wipe, numbers topped out at 1 hours.

What wipe timing does LocalRustServer1337 follow?

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. 32 days 4 hours ago the current world was made.

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): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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?

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

What position does LocalRustServer1337 hold among Rust servers?

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

What is the population on LocalRustServer1337?

LocalRustServer1337 is not responding; status offline, last seen 32 days 1 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 141.98.87.118:28015.

What Rust version is LocalRustServer1337 on?

Version check: Rust network protocol 2633 and build 165217 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 32 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 26 September 2026, recorded by Rust Metrics.

Map and rules

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

Check: gather rate. The name LocalRustServer1337 does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Community server. VAC is off. That is Valve's anti-cheat.

What map is LocalRustServer1337 on?

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

Connection

What do you do to join LocalRustServer1337?

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.