Offline 109.41.179.12:28035 checked 19d ago
Metro v3 test (local)
Connect
srv = rust.server("109.41.179.12:28037")
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 72% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 17:33 UTC19d ago | 0 | NaN | running | 0 |
# 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
- 109.41.179.12:28035
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 17:33 UTC
- hostname
- –
- first seen
- 10 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 491 on average | 72/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 106/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 284 on average | 335/350 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 20/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 419/450 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 253 on average | 304/325 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Metro v3 test (local) rank?
Rank #15,883 on seven-day player hours for Metro v3 test (local), within the top 72% of all ranked servers.
How full does Metro v3 test (local) run?
Metro v3 test (local) returns no live count at this refresh, having last been seen 19 days 7 hours ago.
Server facts
Which Rust version is Metro v3 test (local) on?
Version Rust network protocol 2634 and build 167398 on Windows is reported by Metro v3 test (local). Steam updates your game for you, but the protocol must match to join.
How reliable is Metro v3 test (local), and is it online now?
The latest sample has Metro v3 test (local) offline, with a last sighting 19 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 10 October 2026.
Where does Metro v3 test (local) sit?
For Metro v3 test (local), no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 109.41.179.12:28035.
Rules, settings, map
What rules and settings are recorded for Metro v3 test (local)?
You will not find a gather rate in the string Metro v3 test (local). Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
Wipes and dates
When does Metro v3 test (local) wipe, and on what schedule?
Too few wipes are on record for Metro v3 test (local) to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 19 days 7 hours ago, and that is the one in play.
On Metro v3 test (local), what happens on wipe day?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does Metro v3 test (local) appear among Rust Data lists and filters?
On Rust Data, Metro v3 test (local) appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on Metro v3 test (local)?
The game's server browser reads these tags from Metro v3 test (local): gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. 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 Metro v3 test (local)?
Enter client.connect 109.41.179.12:28035 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.