DWG RG-S13729Server sheetchecked 10m ago
LECKING
Online 85.190.161.161:11300 checked 10m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. The force wipe · high confidence
Coming wipes
- 7d 15hThu 5 Nov, 19:00 UTCFW
- 35d 15hThu 3 Dec, 19:00 UTCFW
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 17:56 UTC FW27d ago | 0 | – | 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.
Similar servers
Quick answers
Server details
What uptime is recorded for LECKING, and is it up?
At this moment LECKING is online. The uptime it reports puts the last restart at about 19 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 1 October 2026.
What does the recorded performance of LECKING show?
The last 48 hours give an average of 10 server fps and a floor of 10. Counted at its highest: 90,029 entities, buildings, deployables and the rest of the world included. Memory use peaked at 2,229 MB. A climbing entity count and low fps are the source of what players feel as lag.
In which location is LECKING hosted?
There is no region published by LECKING. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 85.190.161.161:11300.
On which Rust version is LECKING running?
The platform is Windows and the version is Rust network protocol 2635 and build 168909 on LECKING. The same protocol is required for joining, and Steam updates your game to it.
Counts
How many players are plotted on LECKING?
Current player count on LECKING: 0, of 50 slots. Averaged across seven days, the player count is 0, with a peak of 1. Averaged over the last 48 hours, the player count is highest at 09:00 UTC: 1 players.
What rank has been recorded for LECKING?
Player hours over seven days place LECKING at #13,729, within the top 62% of ranked servers.
Wipe times
What is recorded on LECKING on wipe day?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
What wipe schedule has been recorded for LECKING?
Once a month, with the force wipe, is when LECKING wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 27 days 9 hours ago.
Settings
Which rules and settings are recorded for LECKING?
The name of LECKING records no gather rate. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Community is its tab in the server browser. Anti-cheat: VAC, from Valve, is on.
What is the map for LECKING?
Seed 3452 and size 4,000 define the procedural map LECKING generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Filters
Where does LECKING appear among the Rust Graphs lists and filters?
On Rust Graphs, LECKING is placed in these lists: Rust community servers, plotted. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meaning is attached to each tag on LECKING?
The game's server browser reads these tags from LECKING: gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Connect
What is the way to connect to LECKING?
Connect with client.connect 85.190.161.161:11300: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8
Game
gmvanilla
mp50
ts8
v2635
cs168909
ptrak
$r?
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.
