On air · chart position #13,729
LECKING
Online 85.190.161.161:11300 checked 10m ago
Players
LECKING
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
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
About the server
Is LECKING online, and how reliable is it?
You will find LECKING online at this moment. The uptime it reports puts its last restart about 19 hours ago. Of the past 7 full days it was running for 167 of 168 hours, or 99% of the time. The first record Rust Charts holds of it is 1 October 2026.
Where is LECKING located?
From LECKING, no region is published. Rust Charts doesn't look up where the machine stands; it shows where the server says it is. 85.190.161.161:11300 is its address.
Which version of Rust does LECKING run?
Rust network protocol 2635 and build 168909 on Windows is what LECKING runs. Steam updates your game for you; all you need is the same protocol to join.
Does LECKING run smoothly?
The 48-hour average was 10 server fps; the lowest point was 10. At its fullest it held 90,029 entities: buildings, deployables and the rest of the world. Its memory climbed as high as 2,229 MB. What players feel as lag comes from low fps and an entity count on the rise.
Player counts
How busy is LECKING?
LECKING has 0 of its 50 slots filled right now. Averaging 0 players across seven days, it reached 1 at most. 09:00 UTC was the peak of the last 48 hours, with 1 players on average.
How does LECKING rank against other Rust servers?
In the seven-day player hours table, LECKING is #13,729, inside the top 62% of all ranked servers.
Wipe days
What does wipe day look like on LECKING?
The busiest point of its recent wipes averaged 0 players. 0 hours into the latest wipe, the crowd reached its peak.
What is the wipe schedule on LECKING?
Once a month is the whole of it: LECKING wipes with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. 27 days 9 hours is how long ago its current world was made.
Settings and map
What are the rules and settings on LECKING?
You will not find a gather rate in the name LECKING. The default group size of 8 players applies here. You play survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. The server browser lists it under Community, as a community server. VAC is on: that is Valve's anti-cheat.
Which map does LECKING run?
A procedural map of size 4,000 with seed 3452, generated by the game, is what LECKING runs. You can view it on RustMaps from this page: the same size and seed produce the same map.
Tag guide
Which Rust Charts lists and filters include LECKING?
The Rust Charts lists that carry LECKING are: Rust community servers, unmodded. 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.
What do the server tags on LECKING mean?
These are the tags LECKING makes public, and the server browser reads them: gmvanilla (Game mode): This server runs vanilla survival; mp50 (Max players): It has 50 slots; ts8 (Group limit): Team size is capped at 8, the default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): This server reports build 168909; ptrak (Networking): RakNet handles the network, as standard for the game; $r? (Region code): No region code has been set. The tags also carry the current player count, the queue and when the world was made. You'll find them at the top of this page.
Getting in
How do I join LECKING?
Enter client.connect 85.190.161.161:11300 in the console, which F1 opens once Rust is running. Launch Rust and join on this page is the other way: Rust opens through Steam and connects you.