Offline 76.109.160.102:28115 checked 22d ago
Local Monument Combat Test
Connect
srv = rust.server("76.109.160.102: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()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 76.109.160.102:28115
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 06:45 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 164/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/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 · 93 on average | 69/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Local Monument Combat Test rank?
Over the last seven days Local Monument Combat Test sits at #15,961 on player hours, in the top 71% of ranked servers.
How many players does Local Monument Combat Test hold at once?
Local Monument Combat Test returns no live count at this refresh, having last been seen 22 days 5 hours ago.
About the server
What is the Rust version on Local Monument Combat Test?
The build is Rust network protocol 2634 and build 166652 on Windows, run by Local Monument Combat Test. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local Monument Combat Test, and is it up?
Local Monument Combat Test is offline at this refresh; the last response came 22 days 5 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 6 October 2026.
In which location is Local Monument Combat Test hosted?
For Local Monument Combat Test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 76.109.160.102:28115.
Rules, settings, map
What rules and settings are recorded for Local Monument Combat Test?
No gather rate appears in the name: Local Monument Combat Test. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe data
When does Local Monument Combat Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of Local Monument Combat Test on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 23 days 5 hours ago.
Tags, lists
Which lists on Rust Data hold Local Monument Combat Test, and which filters?
These Rust Data lists include Local Monument Combat Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Local Monument Combat Test?
These tags are published by Local Monument Combat Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Local Monument Combat Test?
In Rust, F1 opens the console: type client.connect 76.109.160.102:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.