Offline 148.113.9.151:36703 checked 6d ago
LEORECORDING
Connect
srv = rust.server("148.113.9.151:36705")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 148.113.9.151:36703
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 11:03 UTC
- hostname
- –
- first seen
- 23 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 514 on average | 454/500 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 440/475 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 286 on average | 928/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 276 on average | 59/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 270 on average | 989/1000 |
| 5 | Rustoria.co - US Main | NA · groups of 16+ · weekly · 236 on average | 22/250 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does LEORECORDING rank?
Over the last seven days LEORECORDING sits at #15,344 on player hours, in the top 69% of ranked servers.
What population does LEORECORDING carry?
The current row shows LEORECORDING offline; the last response was 6 days 4 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does LEORECORDING run?
Rust network protocol 2635 and build 168909 on Linux is what LEORECORDING runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is LEORECORDING, and is it up?
LEORECORDING is offline at this refresh; the last response came 6 days 4 hours ago. 0 of 120 hours up over the last 5 full days, or 0%. Rust Data logged it first on 23 October 2026.
In which location is LEORECORDING hosted?
No region is published by LEORECORDING. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 148.113.9.151:36703.
Settings and map
What rules and settings are recorded for LEORECORDING?
The name LEORECORDING carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Which map has LEORECORDING loaded?
A procedural map runs on LEORECORDING, generated by the game.
Wipe schedule
When does LEORECORDING wipe, and how often?
A rhythm cannot be read from the wipes of LEORECORDING on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 6 days 4 hours ago.
Tags, lists
Where does LEORECORDING appear among Rust Data lists and filters?
The Rust Data lists that LEORECORDING fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on LEORECORDING?
Read by the game's server browser, the tags LEORECORDING publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to LEORECORDING?
The manual route: launch Rust, F1, then client.connect 148.113.9.151:36703. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.