RUST METRICSFlight deck · live data
Data live Servers11,756 Players64,636 Populated3,440 Fresh wipes 3 h196 Scan5 min
‹ All servers213.24.133.133:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 213.24.133.133:28015 checked 44d 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,781no 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 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?

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

Lists and filters

How should you read the tags on LocalRustServer1337?

These are the tags LocalRustServer1337 publishes, and the server browser reads them: 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; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. 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.

Occupancy

What position does LocalRustServer1337 hold among Rust servers?

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

What player count does LocalRustServer1337 carry?

Reading for LocalRustServer1337: offline at this moment; last seen 44 days 19 hours ago.

Server details

Where does LocalRustServer1337 sit?

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

What Rust version is LocalRustServer1337 on?

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

Is LocalRustServer1337 up, and how often does it stay up?

Reading: offline. LocalRustServer1337 last answered 44 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 14 September 2026.

Map and rules

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

No gather rate appears in the name: LocalRustServer1337. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is off.

What map is LocalRustServer1337 on?

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

Connection

How can you get onto LocalRustServer1337?

To join: start Rust, press F1 and type client.connect 213.24.133.133:28015. Or press Launch Rust here and Steam opens the game 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 Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Game build reading: 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.