leander
Offline 62.45.123.205:28015 checked 44d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Rules and settings
On leander, which rules and settings apply?
No gather rate appears in the name leander. 8 players per group is the default limit. Filed under survival, gather, build and raid: the standard game. PvP and raiding are allowed. It is listed under Community in the server browser and is a community server. VAC is on: Valve's anti-cheat is enabled.
What is the map on leander?
A procedural map, generated by the game, is what leander runs.
Tags
Which lists and filters on Rust Server Index is leander filed under?
These lists on Rust Server Index take leander: Community Rust servers, indexed. 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.
How should you read the tags listed for leander?
These are the tags leander publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp10 (Max players): Player cap: 10; ts8 (Group limit): Game default applies: teams of up to 8; v2633 (Protocol): Your client must run protocol 2633 to connect; cs163794 (Build): Build on file: 163794; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): A region code is absent. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
How often is leander wiped, and on what schedule?
The record holds too few of leander's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 44 days 18 hours is when its current world was made.
Player counts
Is leander quiet or crowded?
The last check found leander offline, last seen 44 days 18 hours ago.
Server details
What Rust version is leander on?
Rust network protocol 2633 and build 163794, on Linux, is what leander runs. The protocol must match before you can join, and Steam takes care of updating it.
Is leander reachable, and does it stay up?
The server is down at this moment; the last sighting of leander was 44 days 18 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It was first recorded by Rust Server Index on 13 September 2026.
Which region is leander in?
leander gives no region at all. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 62.45.123.205:28015.
Connecting
What steps lead onto leander?
Two ways in. Type client.connect 62.45.123.205:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp10
ts8
v2633
cs163794
ptrak
$r?
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.