Offline 45.228.67.134:28115 checked 22d ago
FORGE | CORE 2x Trio | LOCAL TEST
Connect
srv = rust.server("45.228.67.134:28117")
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Monday 2 November, 00:01 UTC, in 3d 18h. # Weekly: 7 days after its last wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 45.228.67.134:28115
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 5 Oct 2026, 00:01 UTC
- hostname
- –
- first seen
- 6 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 | Magic Rust #18 — Vanilla 2x | Baйп 28.10 | EU · groups of 150+ · 2x · weekly · 330 on average | 507/570 |
| 1 | MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 | EU · groups of 300+ · 2x · weekly · 313 on average | 43/1000 |
| 2 | Magic Rust #14 — Modded 2x (No limit) | Pyccкий | EU · groups of 300+ · 2x · weekly · 277 on average | 59/100 |
| 3 | MIRAGE RUST | MONDAY 2x | VANILLA+ | Wipe 26.10 | EU · groups of 300+ · 2x · weekly · 274 on average | 88/1900 |
| 4 | РОССИЯ X2 / ДЛЯ НОВИЧКОВ / THIS IS RUST! | EU · groups of 12+ · 2x · weekly · 218 on average | 22/100 |
| 5 | VANILLA x2 | GGRust #4 | Для нoвичкoв 2x | EU · groups of 300+ · 2x · weekly · 129 on average | 10/100 |
Quick answers
From the figures on this page.
Population data
What position does FORGE | CORE 2x Trio | LOCAL TEST take in the server rankings?
Rank #15,986 on seven-day player hours for FORGE | CORE 2x Trio | LOCAL TEST, within the top 71% of all ranked servers.
What population does FORGE | CORE 2x Trio | LOCAL TEST carry?
FORGE | CORE 2x Trio | LOCAL TEST returns no live count at this refresh, having last been seen 22 days 9 hours ago.
Server facts
What Rust version does FORGE | CORE 2x Trio | LOCAL TEST run?
Version Rust network protocol 2634 and build 166652 on Linux is reported by FORGE | CORE 2x Trio | LOCAL TEST. Joining needs the same protocol on your game; Steam handles the update.
How reliable is FORGE | CORE 2x Trio | LOCAL TEST, and is it online now?
Offline now for FORGE | CORE 2x Trio | LOCAL TEST, last seen 22 days 9 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 6 October 2026.
Where does FORGE | CORE 2x Trio | LOCAL TEST sit?
For FORGE | CORE 2x Trio | LOCAL TEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 45.228.67.134:28115 is its address.
Rules, settings, map
Which rules apply on FORGE | CORE 2x Trio | LOCAL TEST, and what settings?
The name carries the figure: FORGE | CORE 2x Trio | LOCAL TEST runs 2x gather. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has FORGE | CORE 2x Trio | LOCAL TEST loaded?
A procedural map runs on FORGE | CORE 2x Trio | LOCAL TEST, generated by the game.
Wipe schedule
When does FORGE | CORE 2x Trio | LOCAL TEST wipe, and on what schedule?
Expect an estimate: FORGE | CORE 2x Trio | LOCAL TEST's next wipe is projected from weekly: 7 days after its last wipe. The schedule puts the next wipe on Monday 2 November at 00:01 UTC. The world it runs now was generated 24 days 5 hours ago. The tags list wipes as weekly.
Tags and filters
Which Rust Data filters and lists contain FORGE | CORE 2x Trio | LOCAL TEST?
The Rust Data lists that FORGE | CORE 2x Trio | LOCAL TEST fits are: Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.
Which meanings do the tags on FORGE | CORE 2x Trio | LOCAL TEST hold?
The game's server browser reads these tags from FORGE | CORE 2x Trio | LOCAL TEST: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^w (Weekly): The interval is one week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into FORGE | CORE 2x Trio | LOCAL TEST?
The manual route: launch Rust, F1, then client.connect 45.228.67.134:28115. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.