Rust Server IndexCard catalogue of Rust servers

Holdings11,659 servers33,003 players78 fresh wipes

Call no.13731 On the shelf · online

LECKING

Online 85.190.161.161:11300 checked 10m ago

Subjects
Players now
0/ 50
0% full
7-day average
0
peak 1
Rank
#13,731
top 62%
Last wipeWiped1 OCT2026 · 27d 10h ago
27d ago · no schedule published
Next wipe
7d 14h
Thu 5 Nov, 19:00 UTC FW
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.250.50.75105:0014:0023:0007:0016:0002:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

02.557.51005:0014:0023:0007:0016:0002: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.

Record sheet C · appended

Rank

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.

Record sheet D · loan terms

Wipe schedule

force wipes only

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

wipe-day peak
0players, last three wipes

Coming wipes

  1. in 7d 14hThu 5 Nov, 19:00 UTCFW
  2. in 35d 14hThu 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.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
1 OCT 2026Thu 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EU
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 549 on average
152/ 250
EU
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average
121/ 200
EU
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average
13/ 250
EU
Rustoria.co - EU MainEU · groups of 16+ · weekly · 284 on average
24/ 250
EU
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average
12/ 100
EU
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average
26/ 200
Reference desk

Quick answers

From the figures on this page.

Settings and map

What settings and rules does LECKING run?

The name of LECKING does not state a gather rate. The default group limit of 8 players applies. Filed under survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. The server browser lists it under Community; it is a community server. VAC, Valve's anti-cheat, is enabled.

Which map is in use on LECKING?

LECKING runs a procedural map of size 4,000 with seed 3452, generated by the game. From this page you can view the map on RustMaps; the same size and seed give the same map.

Tags

On Rust Server Index, which lists and filters carry LECKING?

Filed under these Rust Server Index lists is LECKING: Community Rust servers, indexed. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which tags are attached to LECKING, and what do they stand for?

These are the tags LECKING publishes; the game's server browser reads this list: gmvanilla (Game mode): Unmodified survival rules; mp50 (Max players): Player cap: 50; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): A region code is absent. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipe schedule

What happens on wipe day at LECKING?

Its recent wipes averaged 0 players at peak. 0 hours into the latest wipe, the crowd reached its peak.

When does LECKING wipe?

With the force wipe, LECKING wipes once a month. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, taken by every Rust server. The world it runs now was made 27 days 10 hours.

Player counts

Where does LECKING sit in the rankings?

The seven-day player-hours ranking places LECKING at #13,731, among the top 62% of ranked servers.

What does the player count on LECKING look like?

LECKING is currently showing 0 players on 50 slots. Averaged across seven days: 0 players, peaking at 1. Over the last 48 hours, 09:00 UTC drew the highest average: 1 players.

Operator and status

What version does LECKING use?

Rust network protocol 2635 and build 168909 on Windows is what you will find on LECKING. To join you need the same protocol; Steam handles the update.

What is the uptime and current status of LECKING?

You will find LECKING online as of now. The uptime it reports puts the last restart at about 20 hours ago. It was up 167 of 168 hours across the last 7 full days, or 99% of the time. On 1 October 2026 it was first seen by Rust Server Index.

Is the performance on LECKING good?

Averaged over the last 48 hours, server fps was 10, with a low of 10. The entity count reached 90,029, covering buildings, deployables and all else in the world. Memory use reached as much as 2,229 MB. A climbing entity count and low fps are felt by players as lag.

What is the location of LECKING?

No region is published by LECKING. Rust Server Index takes the server's word for its location and does not look up the machine's position. You will reach it at 85.190.161.161:11300.

Joining the server

What is the way onto LECKING?

Enter client.connect 85.190.161.161:11300 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmvanilla
Game mode Unmodified survival rules.
mp50
Max players Player cap: 50.
ts8
Group limit Game default applies: teams of up to 8.
v2635
Protocol Your client must run protocol 2635 to connect.
cs168909
Build It runs build 168909.
ptrak
Networking RakNet is the network layer, as standard for Rust.
$r?
Region code A region code is absent.

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.