Rust Data LabData lab · live
Live readings Servers11,695 Players53,611 Populated3,212 Fresh wipes · 3h137 Sampled every 5 min

Element card · group Community · atomic number 13,720, its rank

LECKING

Online 85.190.161.161:11300 checked 9m ago

Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak 1
Rank · atomic number#13,720top 62%
Last wipe27d agono schedule published
Next wipe7d 9hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
00.250.50.75110:0019:0004:0013:0023:0008:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
02.557.51010:0019:0004:0013:0023:0008: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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k1 Oct7 Oct12 Oct18 Oct23 Oct29 Oct

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

Reaction kinetics

Wipe schedule

force wipes only

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

wipe-day peak0players, last three wipes

Coming wipes

  1. 7d 9hThu 5 Nov, 19:00 UTCFW
  2. 35d 9hThu 3 Dec, 19:00 UTCFW

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.

Reaction log

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
  1. 1 Ru Rusty Moose |E… 361
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 519 on average 361/ 400
  2. 2 Ru Rustoria.co - … 336
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 336/ 350
  3. 3 Ru Rusty Moose |E… 38
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 38/ 250
  4. 4 Ru Rustoria.co - … 32
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average 32/ 250
  5. 5 Ru Rustafied.com … 48
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 48/ 100
  6. 6 Ru Rustoria.co - … 175
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 244 on average 175/ 200

Quick answers

from the figures on this page

Settings and map

What map is in play on LECKING?

A procedural map of size 4,000 with seed 3452 runs on LECKING, generated by the game. You can view it on RustMaps from this page, since matching size and seed produce the same map.

How is LECKING configured, and what rules apply?

No gather rate appears in the name of LECKING. Groups top out at 8 players, the default for the game. Play runs as survival, raiding, building and gathering: the standard game. You can fight other players and raid them. You will find it under Community in the server browser. The VAC anti-cheat from Valve is enabled.

Server details

Which location is LECKING based in?

No region is published by LECKING. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 85.190.161.161:11300 is the address it uses.

What Rust version does LECKING currently run?

On Windows, LECKING is running Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam takes care of updating it.

Does LECKING stay up, and how reliable is its uptime?

At the moment, LECKING is online. According to the uptime it reports, the last restart was about 2 hours ago. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. It first appeared to Rust Data Lab on 1 October 2026.

Is LECKING known for smooth running?

In the last 48 hours, it averaged 10 server fps, with a low of 10. The maximum entity count was 90,175, covering buildings, deployables and all else in the world. Up to 2,229 MB of memory was used. Players feel lag when fps is low and the entity count climbs.

Wipe days

How often does a wipe happen on LECKING, and at what time?

Once a month is all LECKING wipes, with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is when this server next wipes, along with every other Rust server. 27 days 16 hours ago the current world was made.

What does a typical wipe day on LECKING involve?

At their busiest, recent wipes averaged 0 players. 0 hours after the latest wipe, the crowd peaked.

Where it appears

Which meanings sit behind the tags on LECKING?

gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): It has 50 slots; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): Protocol 2635 is required; join only if your game matches it; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank: that is the tag list LECKING publishes, and the game's server browser reads it. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Which Rust Data Lab filters and lists does LECKING appear in?

These themed Rust Data Lab lists carry LECKING: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player counts

Against other Rust servers, where does LECKING place?

Player hours over the last week put LECKING at #13,720, inside the top 62% of ranked servers.

How full is LECKING right now?

LECKING currently shows 0 players across 50 slots. Averaged over the past week: 0 players, peaking at 1. Peak time in the past 48 hours: 09:00 UTC, when the average was 1 players.

Connection

What is the way to join LECKING?

You can connect by pressing F1 in Rust and entering client.connect 85.190.161.161:11300, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what each one means

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

Game

gmvanilla
Game mode This is vanilla survival.
mp50
Max players It has 50 slots.
ts8
Group limit This uses the game's default: 8 per team.
v2635
Protocol Protocol 2635 is required; join only if your game matches it.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

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.