On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#13,744top 62%
Last wipe27d agono schedule published
Next wipe7d 21hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
38/ 100
F
Working its way up from the back of the class: #13,744 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
17/ 100
F
Needs to work on its frame rate: 10 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
27/ 100
F
Lost ground: down 6,268 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h.
The force wipe · high confidence
wipe-day peak0players, last three wipes
Coming wipes
7d 21hThu 5 Nov, 19:00 UTCFW
35d 21hThu 3 Dec, 19:00 UTCFW
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.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 17:56 UTCFW27d 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for LECKING. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 85.190.161.161:11300.
Is LECKING up, and how steady is its uptime?
The server is up: LECKING is online now. About 14 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
Does LECKING perform well?
It never fell below 10 server fps in the last 48 hours, averaging 10. Buildings, deployables and everything else in the world added up to as many as 90,029 entities. At its highest, it used 2,286 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is LECKING running?
Rust network protocol 2635 and build 168909 on Windows is what LECKING runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does LECKING reset?
The force wipe each month is the only wipe LECKING takes. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 27 days 3 hours.
What happens on LECKING when wipe day arrives?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Population
What position does LECKING hold in the rankings?
Over the last seven days, LECKING has #13,744 for player hours, in the top 62% of all ranked servers.
What does the population on LECKING look like?
Right now, 0 players are on LECKING, which has 50 slots. Averaging 0 players over seven days, it peaked at 1. The busiest time in the last 48 hours was 09:00 UTC, with an average of 1 players.
Tags and filters
What is meant by the tags on LECKING?
The game's browser takes its cue from the tags LECKING has set: gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does LECKING appear in the Rust Server Score lists and filters?
Rust Server Score lists that include LECKING: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is LECKING set up, and what rules does it keep?
You will find no gather rate in the name of LECKING. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on LECKING?
A procedural map of size 4,000 and seed 3452, generated by the game, is what LECKING runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto LECKING?
Enter client.connect 85.190.161.161:11300 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).