LOCAL EXPANSION TEST
Offline 149.154.11.115:28115 checked 21d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 17/ 100
- 214/ 400
- 173/ 225
- 134/ 100
- 249/ 1000
- 20/ 700
Quick answers
Tags and filters
Where does LOCAL EXPANSION TEST appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include LOCAL EXPANSION TEST: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
What's the meaning of the tags on LOCAL EXPANSION TEST?
LOCAL EXPANSION TEST's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp0 (Max players): It holds 0 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): Plugins are handled by Carbon. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What's the location of LOCAL EXPANSION TEST?
LOCAL EXPANSION TEST does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 149.154.11.115:28115.
What's the uptime like for LOCAL EXPANSION TEST?
LOCAL EXPANSION TEST is down at the moment; it was last up 21 days 7 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 26 September 2026.
What Rust version is LOCAL EXPANSION TEST on?
The version on LOCAL EXPANSION TEST is Rust network protocol 2633 and build 165217, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
When does LOCAL EXPANSION TEST wipe?
The wipes recorded for LOCAL EXPANSION TEST are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 22 days 5 hours ago.
Map and rules
Which rules and settings is LOCAL EXPANSION TEST running?
The name of LOCAL EXPANSION TEST contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. Carbon plugins are running here. VAC is on: Valve's anti-cheat is active.
Which map is active on LOCAL EXPANSION TEST?
LOCAL EXPANSION TEST uses a game-generated procedural map.
Player stats
Is LOCAL EXPANSION TEST busy?
The last sighting of LOCAL EXPANSION TEST was 21 days 7 hours ago; it is offline right now.
What's LOCAL EXPANSION TEST's rank among Rust servers?
For player hours in the last seven days, LOCAL EXPANSION TEST ranks #16,897, within the top 72% of ranked servers.
Getting in
How do you get into LOCAL EXPANSION TEST?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 149.154.11.115:28115.