RUST METRICSFlight deck · live data
Data live Servers11,803 Players69,659 Populated3,689 Fresh wipes 3 h126 Scan5 min
‹ All servers148.113.9.151:36703
Offline Full Queue Fresh wipe Wipe due No query

LEORECORDING

Offline 148.113.9.151:36703 checked 4d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,404top 69%
Last wipe4d 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
15k10k15k20k23 Oct24 Oct25 Oct26 Oct27 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

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 LEORECORDING follow?

The rhythm of LEORECORDING's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 4 days 11 hours ago.

Tag meanings

How should you read the tags on LEORECORDING?

These are the tags LEORECORDING publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $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 LEORECORDING?

Rust Metrics lists featuring LEORECORDING: 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; Last wipe: In the last week.

Occupancy

Where does LEORECORDING sit in the rankings?

Ranking for LEORECORDING: #15,404 on seven-day player hours, top 69% of all ranked servers.

What is the population on LEORECORDING?

LEORECORDING is not responding; status offline, last seen 4 days 11 hours ago. Seven-day reading: 0 players on average.

Server

Which location does LEORECORDING run from?

No region tag on LEORECORDING. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 148.113.9.151:36703.

What Rust version is LEORECORDING on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by LEORECORDING. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. LEORECORDING is offline at this moment. Last contact was 4 days 11 hours ago. Uptime for the last 3 full days: 0 of 72 hours, or 0%. The first sighting on Rust Metrics was 23 October 2026.

Settings and map

What settings and rules apply on LEORECORDING?

Check: gather rate. The name LEORECORDING does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is LEORECORDING on?

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

Connection

How do you connect to LEORECORDING?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
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.