Online 157.85.95.94:26929 checked 12m ago
UNILEAVER
Connect
srv = rust.server("157.85.95.94:26930")
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 17 Sep. 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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 6 Oct, 17:34 UTC22d ago | 0 | 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
1000 · seed 1
- map
- Procedural Map
- size
- 1000
- seed
- 1
Server
srv.info()- address
- 157.85.95.94:26929
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 17:34 UTC
- hostname
- –
- first seen
- 13 Sep 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 · 150 on average | 102/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.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 · 118 on average | 120/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 46/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 20/1000 |
Quick answers
From the figures on this page.
Player counts
What position does UNILEAVER take in the server rankings?
Rank #15,338 on seven-day player hours for UNILEAVER, within the top 69% of all ranked servers.
How many players does UNILEAVER hold at once?
The sample now reads 0 players for UNILEAVER, out of 5 slots. Over the last seven days it averaged 0 players.
Server data
How smoothly does UNILEAVER run?
Averaged over 48 hours: 236 server fps, never under 225. The entity count peaked at 4,999, covering buildings, deployables and the rest of the world. The memory field tops out at 1,970 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does UNILEAVER run?
Rust network protocol 2635 and build 166652 on Linux is what UNILEAVER runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is UNILEAVER, and is it online now?
UNILEAVER reports itself online at the current refresh. The uptime it reports puts the last restart about 2 days 14 hours ago. Over the last 7 full days the hours up number 56 of 168, 33%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does UNILEAVER run from?
No region is published by UNILEAVER. 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 157.85.95.94:26929.
Map and rules
What rules and settings are recorded for UNILEAVER?
No gather rate appears in the name: UNILEAVER. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on UNILEAVER?
The game generates the map on UNILEAVER: procedural, size 1,000, seed 1. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does UNILEAVER wipe, and how often?
A rhythm cannot be read from the wipes of UNILEAVER on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 22 days 14 hours ago.
On UNILEAVER, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does UNILEAVER appear among Rust Data lists and filters?
The Rust Data lists that UNILEAVER fits are: 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.
Which meanings do the tags on UNILEAVER hold?
These tags are published by UNILEAVER and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into UNILEAVER?
Enter client.connect 157.85.95.94:26929 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.