Live coverage · Rust server
Offline FORGE | CORE 2x Trio | LOCAL TEST is not on the server list right now. The figures below are from when it was last seen, 22d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Next wipe Monday 2 November, 00:01 UTC, in 3d 12h. Weekly: 7 days after its last wipe
This server has not put up a new map since the desk started watching it.
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.
The next wipe on FORGE | CORE 2x Trio | LOCAL TEST is an estimate, drawn from weekly: 7 days after its last wipe. On Monday 2 November at 00:01 UTC its next wipe falls due. The world you are playing on was built 24 days 11 hours. The tags list wipes as weekly.
These are the Rust Live Stats lists FORGE | CORE 2x Trio | LOCAL TEST fits: 2x Rust servers live now and Modded Rust servers live now. Under the filters Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x it appears on the server list.
These are the tags FORGE | CORE 2x Trio | LOCAL TEST makes public: gmrust (Game mode): Survival here follows standard Rust; mp10 (Max players): The slot count is 10; ts8 (Group limit): Team cap: 8, which is the game default; v2634 (Protocol): You need protocol 2634 on your game to get in; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): No region code is set here; ^w (Weekly): Wipes: every week; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
FORGE | CORE 2x Trio | LOCAL TEST is not online at the moment, having last been seen 22 days 15 hours ago.
On player hours for the past seven days, FORGE | CORE 2x Trio | LOCAL TEST sits at #15,986, inside the top 71% of ranked servers.
Read the name for the rate: 2x gathering on FORGE | CORE 2x Trio | LOCAL TEST. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. You can raid and fight other players. The server browser files it under Modded: plugins or settings alter the game. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.
FORGE | CORE 2x Trio | LOCAL TEST uses a procedural map, which the game generates.
No region is published by FORGE | CORE 2x Trio | LOCAL TEST. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 45.228.67.134:28115.
Rust network protocol 2634 and build 166652 on Linux is what FORGE | CORE 2x Trio | LOCAL TEST runs. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, FORGE | CORE 2x Trio | LOCAL TEST is down, last seen 22 days 15 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. The first sighting by Rust Live Stats was on 6 October 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 45.228.67.134:28115.