Skip to the content
Dive report

LECKING

Online 85.190.161.161:11300 checked 10m ago

Drop in
0/ 50 players now 0% full
07-day averagepeak 2
#7,203ranktop 33%
16d agolast wipeno schedule published
18d 9hnext wipeThu 5 Nov, 19:00 UTC FW

Players

AveragePeak
0123410:0019:0004:0013:0022:0007:00

Hourly average and peak, UTC.

Server performance

02.557.51010:0019:0004:0013:0022:0007: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 Oct4 Oct8 Oct11 Oct15 Oct18 Oct

Top 33% 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 18d 9h. The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

  • 18d 9h
    Thu 5 Nov, 19:00 UTC
    FW

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 FW16d 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.

Neighbouring dive spots

Similar servers

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

From the figures on this page

Quick answers

Tags and search

Where does LECKING appear in Rust Going Deep lists and filters?

These Rust Going Deep lists include LECKING: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the tags on LECKING?

gmvanilla (Game mode): It's vanilla survival; mp50 (Max players): There are 50 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): It's on build 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code — that is the tag list LECKING puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.

Server details

Is LECKING lag-free?

Average server fps for the last 48 hours was 10, and the lowest was 10. At its peak it carried 89,980 entities, including buildings and deployables. 2,326 MB was the highest memory it used. A climbing entity count together with low fps is what feels like lag to players.

Where can you find LECKING?

No region comes from LECKING. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 85.190.161.161:11300.

What's the uptime like for LECKING?

Right now LECKING is online. Its reported uptime shows a restart about 2 hours ago. Over the past full 7 days it stayed up for 168 of 168 hours, or 100%. 1 October 2026 is when Rust Going Deep first saw it.

What is the Rust version for LECKING?

The version on LECKING is Rust network protocol 2634 and build 167781, on Windows. The protocol must match to join; Steam will update your game.

Wipe schedule

When does LECKING wipe?

LECKING limits itself to a single monthly wipe: the force wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives, wiping every Rust server, and that is its next wipe. This world has been running since 16 days 15 hours ago.

What happens on wipe day at LECKING?

The average peak across recent wipes is 0 players. The peak crowd on the latest wipe came 0 hours in.

Settings and map

What settings are in place on LECKING?

Its name does not state a gather rate for LECKING. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. Community is where the server browser puts it, as a community server. The server runs Valve's anti-cheat, VAC.

Which map is active on LECKING?

The map on LECKING is procedural and size 4,000, generated by the game with seed 3452. You can see it on RustMaps from this page, since the same size and seed produce the same map.

Player count

What's the population like on LECKING?

Right now 0 players are on LECKING, which has 50 slots. For the past week, players averaged 0 with a high of 2.

What position does LECKING hold in the server rankings?

For player hours in the last seven days, LECKING ranks #7,203, within the top 33% of ranked servers.

How to join

What's the process to join 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.

What each one means

Server tags

Published as mp50,ptrak,$r?,v2634,gmvanilla,cs167781,ts8

Game

gmvanilla
Game mode It's vanilla survival.
mp50
Max players There are 50 slots on this server.
ts8
Group limit It uses the default team limit: 8.
v2634
Protocol To join, your game has to be on protocol 2634.
cs167781
Build It's on build 167781.
ptrak
Networking RakNet, the network layer Rust uses by default.
$r?
Region code It has no region code.

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.