Rust StatisticsWorking papers on every public Rust server · 39,799 players now

LECKING

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 6m ago · 85.190.161.161:11300

Abstract

We describe the public Rust server LECKING, reached at 85.190.161.161:11300. At the last check it held 0 of 50 places, against a seven-day mean of 0 and a peak of 11. It ranks #13,725 of all servers, the top 62%. It last wiped 27d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Plate 1: The server's own banner, as it publishes it. Table 1 gives its figures at the last check.
Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#13,725top 62%
Last wipe27d agono schedule published
Next wipe37d 11hThu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75108:0017:0002:0011:0021:0006:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
02.557.51008:0017:0002:0011:0021:0006:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 62% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k1 Oct7 Oct12 Oct18 Oct23 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: force wipes only

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak0players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Thu 5 Nov, 19:007d 11hforce wipefw
Thu 3 Dec, 19:0035d 11hforce wipefw
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 1 Oct, 17:56fw27d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of LECKING
Figure 5: The map: Procedural Map, size 4000, seed 3452. Open on RustMaps.
Table 5: The server's published settings.
Address85.190.161.161:11300
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe1 Oct 2026, 17:56 UTC
Hostname–
First seen1 Oct 2026
MapProcedural Map
Size4000
Seed3452

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2] and predicted wipe schedule [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 531 on average258/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average191/225
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average21/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 280 on average22/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average22/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average91/200

Appendix AQuick answers

From the figures on this page.

Server details

A.1How well does LECKING run?

The server fps averaged 10 over the last 48 hours, never dropping below 10. Buildings, deployables and all other world objects counted together reached a maximum of 90,175 entities. The peak memory usage was 2,229 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What location does LECKING have?

A region is not published by LECKING. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 85.190.161.161:11300.

A.3How reliable is LECKING, and is it currently online?

LECKING is currently online. Based on the uptime it reports, the last restart occurred about 44 minutes ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. Its first appearance in Rust Statistics's records is 1 October 2026.

A.4What version of Rust is run on LECKING?

The version of Rust on LECKING is network protocol 2635 and build 168909, and the operating system is Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5When are wipes carried out on LECKING?

The only wipe for LECKING is the monthly force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. The world currently in use was created 27 days 13 hours ago.

A.6What happens on LECKING when wipe day arrives?

Recent wipes saw an average peak of 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.7How does LECKING compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts LECKING at #13,725, within the top 62% of ranked servers.

A.8At what level does LECKING operate in terms of players?

The current population of LECKING is 0, drawn from 50 slots. The peak over seven days is 1, against an average of 0. Averaging 1 players, 09:00 UTC was the busiest hour of the past 48.

Tags and filters

A.9What do the tags associated with LECKING signify?

gmvanilla (Game mode): Survival on vanilla rules; mp50 (Max players): It offers 50 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set: these are the tags LECKING publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.10Where can LECKING be found among the Rust Statistics lists and filters?

The Rust Statistics lists that LECKING fits are: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

A.11Under what rules and settings does LECKING operate?

Its name carries no gather rate for LECKING. The group cap is 8 players, which is the default in the game. survival is the game mode here; gather, build and raid: the standard game. Players may raid and fight one another. Community is its category in the server browser. VAC is active: that is Valve's anti-cheat.

A.12What is the map for LECKING?

Generated by the game from seed 3452, the procedural map on LECKING measures 4,000. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13How do you connect to LECKING?

Press F1 inside Rust to open the console and enter client.connect 85.190.161.161:11300. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. Survival on vanilla rules.
mp50Max players. It offers 50 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. The game build is 168909.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. A region code has not been 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.