Offline 79.137.67.68:28015 checked 1d ago
Lili Test
Connect
srv = rust.server("79.137.67.68: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 18 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 39% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 9h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 9h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 9h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 23 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:25 UTC FW27d ago | 2 | NaN | running | 1 |
| 1 | Sat 19 Sep, 12:17 UTC39d ago | 1 | halved by day 2 | 12.3 days | 1 |
# 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
3500 · seed 1783023111
- map
- Procedural Map
- size
- 3500
- seed
- 1783023111
Server
srv.info()- address
- 79.137.67.68:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 1 Oct 2026, 19:02 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 57/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 24/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 80 on average | 230/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 71 on average | 78/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 66 on average | 10/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 64 on average | 205/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Lili Test take in the server rankings?
Rank #8,712 on seven-day player hours for Lili Test, within the top 39% of all ranked servers.
What population does Lili Test carry?
Offline now for Lili Test, with the last sample 40 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Peak hour in the last 48 hours: 17:00 UTC, mean 0 players.
About the server
How well does Lili Test perform?
The 48-hour average is 90 server fps, with a low of 90. Entity numbers reached 70,762, and that includes buildings, deployables and the rest. Memory peaked at 1,502 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does Lili Test run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Lili Test. Steam updates your game for you, but the protocol must match to join.
How reliable is Lili Test, and is it up?
Offline now for Lili Test, last seen 40 hours ago. Count back 49 minutes from its reported uptime to get the last restart. Uptime of 5% across the last 7 full days: 9 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does Lili Test sit?
There is no region published for Lili Test. 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 79.137.67.68:28015.
Settings and map
Which rules apply on Lili Test, and what settings?
The name Lili Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on Lili Test?
Lili Test runs a procedural map of size 3,500 with seed 1783023111, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does Lili Test wipe, and on what schedule?
A single wipe each month, the force wipe, is all Lili Test does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 27 days 14 hours ago. Its tags carry a monthly wipe schedule.
On Lili Test, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 23 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 2.
Tags and filters
Where does Lili Test appear among Rust Data lists and filters?
On Rust Data, Lili Test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on Lili Test hold?
The game's server browser reads these tags from Lili Test: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Lili Test?
The manual route: launch Rust, F1, then client.connect 79.137.67.68:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.