Online 41.76.213.81:28015 checked 9m ago
LeoZaan
Connect
srv = rust.server("41.76.213.81:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 15 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 48% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 26 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 16:41 UTC12d ago | 5 | NaN | 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.
display(srv.map, srv.info())Map
5000 · seed 337866
- map
- Procedural Map
- size
- 5000
- seed
- 337866
Server
srv.info()- address
- 41.76.213.81:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 16:41 UTC
- hostname
- –
- first seen
- 15 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 163 on average | 49/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 64/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 60/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 16/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does LeoZaan rank?
Player hours over seven days put LeoZaan at #10,611, in the top 48% of the ranked set.
What population does LeoZaan carry?
The sample now reads 0 players for LeoZaan, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 2.
Server facts
How well does LeoZaan perform?
The 48-hour average is 81 server fps, with a low of 64. Buildings, deployables and all else in the world took the count as high as 144,667 entities. The memory field tops out at 4,053 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does LeoZaan run?
Rust network protocol 2635 and build 168909 on Windows is what LeoZaan runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is LeoZaan, and is it up?
LeoZaan reports itself online at the current refresh. Count back 2 days 1 hours from its reported uptime to get the last restart. 144 of 168 hours up over the last 7 full days, or 86%. The first row Rust Data holds for it is dated 15 October 2026.
Which location does LeoZaan run from?
No region is published by LeoZaan. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 41.76.213.81:28015.
Map and rules
Which settings and rules does LeoZaan run?
No gather rate appears in the name: LeoZaan. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has LeoZaan selected?
LeoZaan runs a procedural map of size 5,000 with seed 337866, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does LeoZaan wipe, and how often?
A rhythm cannot be read from the wipes of LeoZaan on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 12 days 7 hours ago.
What is wipe day on LeoZaan like?
Recent wipes averaged 5 players at their peak. The crowd on the latest wipe topped out 26 hours after it began.
Tags, lists
Which lists on Rust Data hold LeoZaan, and which filters?
On Rust Data, LeoZaan appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on LeoZaan?
Read by the game's server browser, the tags LeoZaan publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to LeoZaan?
In Rust, F1 opens the console: type client.connect 41.76.213.81:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.