Skip to the page
Network live 11,697 servers online 44,561 players aboard 101 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

LECKING

Online 85.190.161.161:11300 checked 11m ago

Tracking number · connect
Wipe progress · wiped 27d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Thu 5 Nov, 19:00 UK Thu 5 Nov, 19:00 UTC FW in 7d 17h · high confidence
0/ 50 players now 0% full
07-day averagepeak 1
#13,740ranktop 62%
27d agolast wipeno schedule published
7d 17hnext wipeThu 5 Nov, 19:00 UTC FW
Delivery history

Players, performance and rank

Players

AveragePeak
00.250.50.75102:0011:0020:0004:0013:0023:00

Hourly average and peak, UTC.

Server performance

0510152002:0011:0020:0004:0013:0023: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 Oct7 Oct12 Oct18 Oct23 Oct29 Oct

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

Wipe schedule

force wipes only
Next delivery expected

Next wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 7d 17h.

The force wipe · high confidence
0wipe-day peakplayers, last three wipes

Coming wipes

  1. 7d 17hThu 5 Nov, 19:00 UTC19:00 UKFW
  2. 35d 17hThu 3 Dec, 19:00 UTC19:00 UKFW

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

every wipe as a delivery, newest first
  1. Thu 5 Nov, 19:00 UTC FW19:00 UK · in 7d 17h
    Next wipe expected · the force wipe
  2. Thu 1 Oct, 17:56 UTC FW 18:56 UK · 27d ago
    Force wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    running
    Players before
    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 parcels

Similar servers

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

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 565 on average 237 / 275
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average 138 / 200
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average 27 / 250
  4. Rustoria.co - EU MainEU · groups of 16+ · weekly · 289 on average 14 / 250
  5. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average 30 / 100
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average 0 / 200
Help desk

Quick answers

From the figures on this page.

Player activity

What is the ranking of LECKING against other Rust servers?

In the top 62% of all ranked servers sits LECKING, at #13,740 on hours played over seven days.

What is the current population on LECKING?

At the moment 0 players are on LECKING, which has 50 slots. Averaged over the past week: 0 players, peaking at 1. The busiest hour over the last 48 hours was 09:00 UTC, averaging 1 players.

Map and rules

On what map does LECKING take place?

The game generates the procedural map on LECKING at size 4,000 with seed 3452. Size and seed match means the map matches, so you can view it on RustMaps from this page.

What settings and rules should you know for LECKING?

The name of LECKING gives no gather rate. 8 players is the group limit, since the game's default applies. You get survival here, the usual game: build, gather, raid. Fighting and raiding between players is allowed. The server browser files it under Community, as a community server. The VAC anti-cheat from Valve is enabled.

Server details

In which region is LECKING based?

You will find no region published by LECKING. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. You will find it at 85.190.161.161:11300.

How smoothly does LECKING run?

The 48-hour average for server fps stands at 10, never dipping below 10. Buildings, deployables and all the rest of the world pushed its entity count as high as 90,029. 2,229 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.

How reliable is LECKING, and is it currently online?

LECKING is up and online at the moment. The uptime it reports puts its last restart at about 17 hours ago. It was up 167 of 168 hours over the last 7 full days, 99% of the time. 1 October 2026 is when Rust Wipe Tracker first recorded it.

On what Rust version does LECKING operate?

On Windows, LECKING runs Rust network protocol 2635 and build 168909. The same protocol is required to join, and Steam takes care of updating it.

Wipe schedule

What happens on LECKING when wipe day arrives?

The average busiest point of its recent wipes was 0 players. After 0 hours the latest wipe's crowd hit its peak.

When does LECKING wipe? What schedule does it follow?

LECKING wipes with the force wipe and at no other time, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. You are playing a world created 27 days 7 hours.

Tags and filters

Where does LECKING appear across the Rust Wipe Tracker lists and filters?

These Rust Wipe Tracker lists take LECKING: Rust community servers, unmodded. On the server list, apply Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it appears.

How should you read the tags on LECKING?

gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): No region code is set are the tags LECKING publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

How to join

What steps do you take to join LECKING?

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, 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 Survival in vanilla form.
mp50
Max players Slot count: 50.
ts8
Group limit Team limit: 8, the standard default.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code No region code is 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.