Online 85.190.161.161:11300 checked 11m ago
LECKING
Connect
srv = rust.server("85.190.161.161:11301")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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, measured since 1 Oct. 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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 15h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:56 UTC FW27d ago | 0 | NaN | running | 0 |
# 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
4000 · seed 3452
- map
- Procedural Map
- size
- 4000
- seed
- 3452
Server
srv.info()- address
- 85.190.161.161:11300
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:56 UTC
- hostname
- –
- first seen
- 1 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 · 555 on average | 135/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 116/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 12/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 286 on average | 23/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 10/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 250 on average | 19/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does LECKING rank?
Over the last seven days LECKING sits at #13,729 on player hours, in the top 62% of ranked servers.
How many players does LECKING hold at once?
LECKING reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 09:00 UTC is the busiest, at 1 players.
Server facts
What does performance look like on LECKING?
Averaged over 48 hours: 10 server fps, never under 10. Entity numbers reached 90,029, and that includes buildings, deployables and the rest. A high of 2,229 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does LECKING run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by LECKING. Joining needs the same protocol on your game; Steam handles the update.
How reliable is LECKING, and is it online now?
LECKING reports itself online at the current refresh. Count back 20 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 1 October 2026.
Where does LECKING sit?
No region is published by LECKING. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 85.190.161.161:11300.
Settings and map
What rules and settings are recorded for LECKING?
No gather rate appears in the name: LECKING. 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. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
What is the map on LECKING?
The game generates the map on LECKING: procedural, size 4,000, seed 3452. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does LECKING wipe, and on what schedule?
Once a month LECKING wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 27 days 9 hours ago.
What is wipe day on LECKING like?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Where does LECKING appear among Rust Data lists and filters?
The Rust Data lists that LECKING 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.
Which meanings do the tags on LECKING hold?
Read by the game's server browser, the tags LECKING publishes are: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to LECKING?
Enter client.connect 85.190.161.161:11300 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.