Offline 122.40.171.64:28025 checked 13d ago
BUNDANG_LOCAL_SPAWNFIX
Connect
srv = rust.server("122.40.171.64:28025")
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 70% 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 09:59 UTC14d ago | 1 | 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
- 122.40.171.64:28025
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 09:59 UTC
- hostname
- –
- first seen
- 15 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 · 516 on average | 441/475 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 355/375 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 42/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 33/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 49/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 243 on average | 152/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does BUNDANG_LOCAL_SPAWNFIX rank?
Player hours over seven days put BUNDANG_LOCAL_SPAWNFIX at #15,114, in the top 70% of the ranked set.
How full does BUNDANG_LOCAL_SPAWNFIX run?
Offline now for BUNDANG_LOCAL_SPAWNFIX, with the last sample 13 days 1 hours ago.
Server facts
What Rust version does BUNDANG_LOCAL_SPAWNFIX run?
The build is Rust network protocol 2634 and build 167781 on Windows, run by BUNDANG_LOCAL_SPAWNFIX. Steam updates your game for you, but the protocol must match to join.
How reliable is BUNDANG_LOCAL_SPAWNFIX, and is it up?
The latest sample has BUNDANG_LOCAL_SPAWNFIX offline, with a last sighting 13 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 15 October 2026.
Where does BUNDANG_LOCAL_SPAWNFIX sit?
For BUNDANG_LOCAL_SPAWNFIX, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 122.40.171.64:28025 is its address.
Map and rules
Which rules apply on BUNDANG_LOCAL_SPAWNFIX, and what settings?
No gather rate appears in the name: BUNDANG_LOCAL_SPAWNFIX. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Wipe data
When does BUNDANG_LOCAL_SPAWNFIX wipe, and how often?
Too few wipes are on record for BUNDANG_LOCAL_SPAWNFIX 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. The world it runs now was generated 14 days 1 hours ago.
On BUNDANG_LOCAL_SPAWNFIX, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold BUNDANG_LOCAL_SPAWNFIX, and which filters?
On Rust Data, BUNDANG_LOCAL_SPAWNFIX appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on BUNDANG_LOCAL_SPAWNFIX hold?
These tags are published by BUNDANG_LOCAL_SPAWNFIX and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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
How can I connect to BUNDANG_LOCAL_SPAWNFIX?
The manual route: launch Rust, F1, then client.connect 122.40.171.64:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.