Offline 51.91.242.62:28100 checked 18d ago
LushMap test
Connect
srv = rust.server("51.91.242.62:28102")
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. 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 72% 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 | Sun 11 Oct, 04:48 UTC18d 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 51.91.242.62:28100
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 10:22 UTC
- hostname
- –
- first seen
- 11 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 · 150 on average | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 83/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 256/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 350/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does LushMap test rank?
Rank #15,826 on seven-day player hours for LushMap test, within the top 72% of all ranked servers.
What population does LushMap test carry?
The current row shows LushMap test offline; the last response was 18 days 5 hours ago.
Server facts
What is the Rust version on LushMap test?
Version Rust network protocol 2634 and build 167398 on Linux is reported by LushMap test. Steam updates your game for you, but the protocol must match to join.
Is LushMap test up, and what does its uptime show?
LushMap test is offline at this refresh; the last response came 18 days 5 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 11 October 2026.
Which location does LushMap test run from?
There is no region published for LushMap test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 51.91.242.62:28100 is its address.
Map and rules
Which settings and rules does LushMap test run?
No gather rate appears in the name: LushMap test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
When does LushMap test wipe, and on what schedule?
Too few wipes are on record for LushMap test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 18 days 5 hours ago, and that is the one in play.
On LushMap test, what happens on wipe day?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Which lists on Rust Data hold LushMap test, and which filters?
These Rust Data lists include LushMap test: 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.
How should you read the server tags on LushMap test?
Read by the game's server browser, the tags LushMap test publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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
What is the way to join LushMap test?
Enter client.connect 51.91.242.62:28100 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.