Rust Server Analytics 60,085 players11,768 servers
All servers
Drill-through Server detail

LECKING

Online 85.190.161.161:11300 checked 9m ago

Drill-through
FilterServeris LECKING
Attributes
Last refreshed
Players now 0/ 50
7-day average 0 peak 1
Rank #13,742 top 62%
Last wipe 27d ago no schedule published
Next wipe 7d 20h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.250.50.75123:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
0510152023:0008:0017:0002:0011:0021:00

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
RankRank in region
15k10k15k20k1 Oct6 Oct12 Oct17 Oct23 Oct28 Oct

Top 62% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

InWhen, UTCKind
7d 20hThu 5 Nov, 19:00 UTCFW force wipe
35d 20hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 554 on average 410 / 500
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average 274 / 300
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 295 on average 40 / 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 294 on average 35 / 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 273 on average 76 / 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 252 on average 92 / 200

Quick answers

from the figures on this page

Wipe cycle

The wipe schedule for LECKING: what is it?

The force wipe is the only wipe for LECKING, once a month. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The world now in play was created 27 days 4 hours ago.

On LECKING, what happens on wipe day?

Recent wipes averaged a busiest count of 0 players. Peak population for the latest wipe came 0 hours after it began.

Server

In which region does LECKING sit?

A region is not published by LECKING. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 85.190.161.161:11300.

Which Rust version is LECKING on?

Rust network protocol 2635 and build 168909 on Windows is the setup for LECKING. The protocol has to match before you can join; Steam updates it automatically.

How reliable is LECKING, and is it online now?

LECKING reports online at the current check. Its reported uptime indicates a restart roughly 15 hours ago. Of 168 hours in the last 7 full days, 168 were up: 100%. 1 October 2026 is when Rust Server Analytics first recorded it.

Is performance on LECKING stable?

Over 48 hours the average held at 10 server fps, and the minimum was 10. At its highest the entity count was 90,029, including buildings, deployables and all else. At its highest, memory use was 2,286 MB. Lag, for players, means low fps alongside a growing entity count.

Tags

Which meanings do the tags on LECKING carry?

Tags from LECKING, as read by the game's server browser, are: gmvanilla (Game mode): The vanilla survival format; mp50 (Max players): Player slots: 50; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On Rust Server Analytics, which lists and filters feature LECKING?

These Rust Server Analytics lists include LECKING: Community Rust servers, live. It appears on the server list under the following filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does LECKING hold in the server rankings?

Player hours for the last seven days place LECKING at #13,742, in the top 62% of the ranked field.

What is the population of LECKING?

Of 50 slots, 0 are filled on LECKING at this refresh. Averaging 0 players across seven days, the server reached a peak of 1. Averaged over 48 hours, activity is highest at 09:00 UTC with 1 players.

Map and rules

How is LECKING configured, and what rules apply?

No gather rate is given in the name of LECKING. No custom group limit: 8 players is the standard. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser, it appears under Community. Anti-cheat status: VAC on.

The map on LECKING: which one is it?

A procedural map of size 4,000 with seed 3452, generated by the game, runs on LECKING. Size and seed fix the map, so a RustMaps view is available from this page.

Connection

How do you connect to LECKING?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 85.190.161.161:11300.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode The vanilla survival format.
mp50
Max players Player slots: 50.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code A region code is not set.

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.