Open every day, at every hour Admission free 11,645 servers and 42,938 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

The server's own banner, as it publishes it

Exhibit no. 13,731Acc. 2026.13731

LECKING

Rust server · in the archive since 1 October 2026

Online 85.190.161.161:11300 checked 13m ago

To visit
Players now 0/ 50
0% full
7-day average0peak 1
Rank#13,731top 62%
Last wipe27d agoThu 1 Oct, 17:56 UTC · no schedule published
Next wipe7d 10hThu 5 Nov, 19:00 UTC FW

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectednow, 29 Oct 2026, 08:05 UTCAll times UTC.

The record of each wipe

  1. Thu 1 Oct 202617:56 UTC FW27d ago
    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.

The rhythm

Wipe schedule

force wipes only

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

0wipe-day peakplayers, last three wipes

Coming wipes

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

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

AveragePeak
00.250.50.75109:0018:0003:0011:0021:0006:00

Hourly average and peak, UTC.

Folder 2

Server performance

02.557.51009:0018:0003:0011:0021:0006: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.

Folder 3

Rank

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.

Related exhibits

Similar servers

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

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags and filters

What do the server tags on LECKING mean?

These tags from LECKING, read by the game's server browser, are: gmvanilla (Game mode): Vanilla survival is the mode; mp50 (Max players): Slot count: 50; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The server has no region code. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.

Which Rust Server History lists and filters include LECKING?

The Rust Server History lists that feature LECKING are: Rust community servers. 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.

The record

Does LECKING run smoothly?

Across the last 48 hours it averaged 10 server fps; the low was 10. As many as 90,175 entities were in the world: buildings, deployables and the rest. Memory use peaked at 2,229 MB. Lag, as players feel it, has two sources: low fps and a rising entity count.

Which version of Rust does LECKING run?

Rust network protocol 2635 and build 168909 is the build LECKING runs, on Windows. The protocol must match to join, and Steam handles that update.

Is LECKING online, and how reliable is it?

At this moment LECKING is online. Going by its reported uptime, it restarted about 44 minutes ago. It was up for 167 of 168 hours in the last 7 full days, 99% of the time. First seen by Rust Server History on 1 October 2026.

Where is LECKING located?

There is no region published by LECKING. Rust Server History does not look up where the machine stands; it shows where a server says it is. You can reach it at 85.190.161.161:11300.

Wipe log

What does wipe day look like on LECKING?

0 players on average was the busiest its recent wipes drew. On the latest wipe, 0 hours after the wipe, the crowd peaked.

What is the wipe schedule on LECKING?

The force wipe is the only wipe on LECKING, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 27 days 14 hours ago its current world was made.

Population

How does LECKING rank against other Rust servers?

Over seven days of player hours, LECKING ranks #13,731, inside the top 62% of all ranked servers.

How busy is LECKING?

Against 50 slots, LECKING records 0 players right now. A seven-day average of 0 players is recorded, with a peak of 1. Stored history puts the busiest hour of the past 48 at 09:00 UTC, averaging 1 players.

Map and rules

What are the rules and settings on LECKING?

No gather rate is stated in the name of LECKING. The limit of 8 players per group is the game's default. survival is the game mode, the usual game, with gathering, building and raiding. Fighting and raiding between players are permitted. Under Community in the server browser, this community server is listed. The anti-cheat VAC from Valve is active.

Which map does LECKING run?

A procedural map of size 4,000 with seed 3452 is what LECKING runs, generated by the game. You can look at the map on RustMaps from this page, since one size and seed always give one map.

How to join

How do I join LECKING?

Entering client.connect 85.190.161.161:11300 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmvanilla
Game mode Vanilla survival is the mode.
mp50
Max players Slot count: 50.
ts8
Group limit The game default caps teams at 8.
v2635
Protocol To join, your game has to be on protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet handles the network layer, as standard for the game.
$r?
Region code The server 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.