RUST METRICSFlight deck · live data
Data live Servers11,716 Players60,383 Populated3,374 Fresh wipes 3 h178 Scan5 min
‹ All servers213.24.133.152:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 213.24.133.152:28015 checked 42d 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,834no region published
Last wipe44d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep
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

Reset cycle

What wipe timing does LocalRustServer1337 follow?

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 44 days 18 hours ago.

Tag meanings

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

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): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from LocalRustServer1337. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does LocalRustServer1337 appear in Rust Metrics lists and filters?

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

Where does LocalRustServer1337 sit in the rankings?

Ranking for LocalRustServer1337: #13,834 on seven-day player hours, top – of all ranked servers.

How full does LocalRustServer1337 get?

LocalRustServer1337 is not responding; status offline, last seen 42 days 1 hours ago.

Server details

Which location does LocalRustServer1337 run from?

No region tag on LocalRustServer1337. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 213.24.133.152:28015.

What Rust version is LocalRustServer1337 on?

Rust network protocol 2633 and build 163794 on Windows is the build LocalRustServer1337 runs. Matching protocol is required to join. Let Steam update your game.

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

LocalRustServer1337 reports offline. The last reading came 42 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 September 2026.

Settings and map

What settings and rules apply on LocalRustServer1337?

Check: gather rate. The name LocalRustServer1337 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is off. That is Valve's anti-cheat.

Which map is live on LocalRustServer1337?

The game generates a procedural map for LocalRustServer1337.

Join

How do you connect to LocalRustServer1337?

Check: join. Open Rust, press F1, then enter client.connect 213.24.133.152: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?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.