Rust Server TrendsSeismic network · station log
Recording Stations11,525 Players85,836 Active3,992 Wipes · 3 h134 48 h

Station XX-15454 · recording

LECKING

Online 85.190.161.161:11300 checked 5m ago

Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak –
Rank
#15,454
top 70%
Last wipe
15d ago
no schedule published
Next wipe
12d 5h
Thu 3 Dec, 19:00 UTC FW
Seismic record · station XX-15454 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

0123411:0011:2511:4512:1012:3012:55

Every five minutes, from the Steam server list.

Channel 2 · instrument health

Server performance

02.557.51014:0023:0008:0017:0002:0011: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct11 Oct21 Oct31 Oct10 Nov20 Nov

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

Expected events

Wipe schedule

force wipes only

Next wipe Thursday 3 December, 19:00 UTC, in 12d 5h. The force wipe · high confidence

usual gap
35 daysbetween real wipes
wipe-day peak
0players, last three wipes

Coming wipes

  1. 12d 5hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Thu 5 NovThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 5 Nov, 18:48 UTC FW15d ago M0.0steady 0 – running 0
Thu 1 Oct, 17:56 UTC FW50d ago M0.0steady 0 – 35 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 403 on average
596/ 600
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 295 on average
595/ 600
Rusty Moose |US Monthly| NA · groups of 12+ · monthly · 275 on average
123/ 200
Rustoria.co - EU Long EU · groups of 14+ · monthly · 248 on average
247/ 250
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 233 on average
72/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 232 on average
575/ 600
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on LECKING?

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

Which settings and rules apply on LECKING?

The name of LECKING gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on LECKING?

0 of the 50 slots on LECKING are filled right now. Averaged across the last seven days, the population was 0 players.

How does LECKING rank against other Rust servers?

Over the last seven days, LECKING recorded enough player hours to reach #15,454 worldwide, placing it in the top 70% of all ranked servers.

Server facts

How reliably does LECKING stay online?

As recorded now, LECKING is running. The uptime it reports puts its last restart about 5 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. On 1 October 2026 it was recorded for the first time by Rust Server Trends.

Does LECKING hold a steady tick rate?

The 48-hour average is 10 server fps; 10 is the lowest observed. At its highest, it carried 88,000 entities: buildings, deployables and the world's other contents. Its highest memory use was 1,797 MB. Low fps together with a growing entity count is what players experience as lag.

Where in the world is LECKING hosted?

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

Which Rust version is LECKING running?

LECKING is running Rust network protocol 2636 and build 127089 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on LECKING?

The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.

On what timetable does LECKING run its wipes?

The force wipe is the only wipe LECKING takes, once a month. Every Rust server wipes at the force wipe on Thursday 3 December at 19:00 UTC, which is its next wipe. The present world dates from 15 days 18 hours.

Lists and tags

What do the server tags on LECKING mean?

The game's server browser reads the tags LECKING publishes: gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2636 (Protocol): Game protocol 2636: to join, your game must match this version; cs127089-84fd9a97663 (Build): You won't find a published build number; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does LECKING appear?

These Rust Server Trends lists include LECKING: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

What steps get you onto LECKING?

You can connect by pressing F1 in Rust and typing client.connect 85.190.161.161:11300 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2636,gmvanilla,cs127089-84fd9a97663,ts8

Game

gmvanilla
Game mode Survival in vanilla mode.
mp50
Max players Slots: 50.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2636
Protocol Game protocol 2636: to join, your game must match this version.
cs127089-84fd9a97663
Build You won't find a published build number.
ptrak
Networking The network layer is RakNet, the game's standard.
$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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.