Statistical profileOnline
LECKING
85.190.161.161:11300 checked 11m ago
Connect to this server
1. Main points
Players now
0/ 50
0% full
7-day average
0
peak 1
Rank
#13,722
top 62%
Last wipe
27d ago
no schedule published
Next wipe
7d 12h
Thu 5 Nov, 19:00 UTC FW
Main points
- There were 0 players on it, 0% of its 50 slots.
- Over the last seven days it averaged 0 players, with a peak of 1.
- It ranks #13,722 of all ranked servers, the top 62%, on player hours over the last seven days.
- Its current map went up 27d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
2. Players
Figure 1: Players on LECKING
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternforce wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. The force wipe · high confidence
Wipe-day peak
0
players, last three wipes
Table 1: Coming wipes
Expected from its own rhythm and the force wipe
| In | Date and time | Kind |
|---|---|---|
| 7d 12h | Thu 5 Nov, 19:00 UTC | Force wipe FW |
| 35d 12h | Thu 3 Dec, 19:00 UTC | Force wipe FW |
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 2: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 17:56 UTC FW27d ago | 0 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of LECKING
4000 · seed 3452
8. Server characteristics
Table 4: Characteristics of LECKING
What the server publishes and what was recorded
| Address | 85.190.161.161:11300 |
|---|---|
| Region | – |
| Max players | 50 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 1 Oct 2026, 17:56 UTC |
| Hostname | – |
| First seen | 1 Oct 2026 |
9. Similar servers
Table 5: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 537 on average | 196 / 250 |
| Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 182 / 200 |
| Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 16 / 250 |
| Rustoria.co - EU Main | EU · groups of 16+ · weekly · 281 on average | 15 / 250 |
| Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 16 / 100 |
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 248 on average | 90 / 200 |
10. Quick answers
From the figures on this page.
Wipe records
On what schedule are wipes carried out on LECKING?
A monthly force wipe is the sole occasion on which LECKING wipes. Its next wipe is due on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. This world was generated 27 days 12 hours ago.
On LECKING, what happens on wipe day?
The average busiest point of its recent wipes drew 0 players. On the latest wipe, 0 hours passed before the crowd peaked.
About the server
Is LECKING up, and how well has it held up?
This release records LECKING as online. About 23 hours ago is when it last restarted, according to the uptime it reports. A total of 167 of 168 hours were up over 7 full days, which is 99% of the time. It was first seen by Rust Census on 1 October 2026.
What does the performance record of LECKING show?
Average server fps over the last 48 hours was 10, with a low of 10. Buildings, deployables and everything else in the world took the entity count to 90,175. Memory use reached 2,229 MB at its peak. Players feel low fps and a rising entity count as lag.
In which location is LECKING based?
A region is not published by LECKING. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 85.190.161.161:11300 is its address.
What version of Rust has been recorded on LECKING?
This release lists LECKING on Rust network protocol 2635 and build 168909, running on Windows. Steam updates your game for you, but it has to be on the same protocol to join.
Population
What population has been recorded on LECKING?
The present count is 0 players on LECKING, out of 50 slots. This release records a seven-day average of 0 players and a peak of 1. Over the past 48 hours the highest average fell at 09:00 UTC: 1 players.
In the rankings of Rust servers, where is LECKING placed?
For seven-day player hours, LECKING is ranked #13,722, placing it in the top 62% of all ranked servers.
Lists and tags
Which Rust Census filters and lists cover LECKING?
These Rust Census lists include LECKING: Community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is meant by each tag shown on LECKING?
These are the tags LECKING publishes for the game's server browser to read: gmvanilla (Game mode): Survival play in the vanilla format; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): Protocol 2635 is required; a different version cannot join; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Settings and map
Which map is in use on LECKING?
Size 4,000 and seed 3452: that is the procedural map on LECKING, generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page.
On LECKING, what rules and settings are in force?
No gather rate is given in the name of LECKING. 8 players is the group limit, the game's default. survival is the game mode recorded, the standard game: gather, build, raid. Fighting other players and raiding are allowed. It appears under Community in the server browser. VAC, Valve's anti-cheat, is enabled.
Connecting
How can you connect to LECKING?
You can open the console in Rust with F1 and enter client.connect 85.190.161.161:11300; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8
Game
gmvanilla | Game mode Survival play in the vanilla format. |
|---|---|
mp50 | Max players 50 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol Protocol 2635 is required; a different version cannot join. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$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.