LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Force wipe
Thursday 1 October 2026, 17:56 UTC FW
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.
At their busiest, its recent wipes averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Nothing wipes LECKING but the force wipe, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 27 days 20 hours have passed since this world was generated.
These are the Rust Live Stats lists LECKING fits: Live Rust community servers. You will find it on the server list under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
The server browser reads gmvanilla (Game mode): Survival in the vanilla style; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set, which LECKING publishes. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
LECKING is carrying 0 players at the moment, with 50 slots in total. Peak over the past week: 1. Average: 0 players. Peak hour over 48 hours: 09:00 UTC, at 1 players on average.
Player hours over seven days put LECKING at #13,714, in the top 62% of all ranked servers.
Nothing in the name of LECKING states a gather rate. The default applies: 8 players to a group. survival applies here, the standard game: gather, build, raid. You can raid and fight other players. Community is its browser category. VAC is enabled: Valve's anti-cheat.
LECKING runs a game-generated procedural map: size 4,000, seed 3452. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on LECKING states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 85.190.161.161:11300.
It never went below 10 server fps in the last 48 hours, averaging 10. Buildings, deployables and everything else in the world added up to a maximum of 90,175 entities. Up to 2,229 MB of memory was used. A climbing entity count and low fps are felt as lag by players.
Rust network protocol 2635 and build 168909 on Windows is what LECKING runs. To join, your game must use the same protocol; Steam handles the update for you.
Right now LECKING is online. Based on the uptime it reports, the last restart was about 7 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. The first sighting by Rust Live Stats was on 1 October 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 85.190.161.161:11300.
