Offline 37.27.108.215:7043 checked 16d ago
MULTI-RUST MAX4|X2|TP|KIT|EVENT|
Connect
srv = rust.server("37.27.108.215:7044")
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 best
Top 61% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 13 Oct, 11:12 UTC16d ago | 1 | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 37.27.108.215:7043
- region
- –
- max players
- 300
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 13 Oct 2026, 11:12 UTC
- hostname
- –
- first seen
- 13 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 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 815 on average | 569/700 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 614 on average | 1288/1475 |
| 2 | Atlas - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 381 on average | 143/200 |
| 3 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 351 on average | 707/790 |
| 4 | Magic Rust #18 — Vanilla 2x | Baйп 28.10 | EU · groups of 150+ · 2x · weekly · 336 on average | 540/680 |
| 5 | MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 | EU · groups of 300+ · 2x · weekly · 319 on average | 68/1000 |
Quick answers
From the figures on this page.
Population data
How does MULTI-RUST MAX4|X2|TP|KIT|EVENT| compare in the rankings?
Rank #13,213 on seven-day player hours for MULTI-RUST MAX4|X2|TP|KIT|EVENT|, within the top 61% of all ranked servers.
How many players does MULTI-RUST MAX4|X2|TP|KIT|EVENT| hold at once?
Offline now for MULTI-RUST MAX4|X2|TP|KIT|EVENT|, with the last sample 16 days 9 hours ago.
About the server
What Rust version does MULTI-RUST MAX4|X2|TP|KIT|EVENT| run?
Rust network protocol 2634 and build 167781 on Linux is what MULTI-RUST MAX4|X2|TP|KIT|EVENT| runs. The protocol has to match before you can join, and Steam does the updating.
Is MULTI-RUST MAX4|X2|TP|KIT|EVENT| up, and what does its uptime show?
Offline now for MULTI-RUST MAX4|X2|TP|KIT|EVENT|, last seen 16 days 9 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 October 2026.
Which location does MULTI-RUST MAX4|X2|TP|KIT|EVENT| run from?
There is no region published for MULTI-RUST MAX4|X2|TP|KIT|EVENT|. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 37.27.108.215:7043 is its address.
Rules, settings, map
Which rules apply on MULTI-RUST MAX4|X2|TP|KIT|EVENT|, and what settings?
The name carries the figure: MULTI-RUST MAX4|X2|TP|KIT|EVENT| runs 2x gather. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has MULTI-RUST MAX4|X2|TP|KIT|EVENT| selected?
MULTI-RUST MAX4|X2|TP|KIT|EVENT| runs a procedural map, which the game generates.
Wipe schedule
When does MULTI-RUST MAX4|X2|TP|KIT|EVENT| wipe, and on what schedule?
A rhythm cannot be read from the wipes of MULTI-RUST MAX4|X2|TP|KIT|EVENT| 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. This world was created 16 days 10 hours ago.
What is wipe day on MULTI-RUST MAX4|X2|TP|KIT|EVENT| like?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does MULTI-RUST MAX4|X2|TP|KIT|EVENT| appear among Rust Data lists and filters?
On Rust Data, MULTI-RUST MAX4|X2|TP|KIT|EVENT| appears in these lists: Modded Rust servers and 2x 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; Gather rate: 2x.
Which meanings do the tags on MULTI-RUST MAX4|X2|TP|KIT|EVENT| hold?
These tags are published by MULTI-RUST MAX4|X2|TP|KIT|EVENT| and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp300 (Max players): The server lists 300 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into MULTI-RUST MAX4|X2|TP|KIT|EVENT|?
Enter client.connect 37.27.108.215:7043 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.