Offline 122.40.171.64:28065 checked 13d ago
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Connect
srv = rust.server("122.40.171.64:28066")
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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 21:52 UTC13d 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
- 122.40.171.64:28065
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 21:52 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 · 537 on average | 162/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 154/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 15/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 281 on average | 15/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 16/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 248 on average | 74/200 |
Quick answers
From the figures on this page.
Population
How does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION compare in the rankings?
Rank #15,101 on seven-day player hours for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, within the top 70% of all ranked servers.
How full does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run?
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION returns no live count at this refresh, having last been seen 13 days 7 hours ago.
About the server
Which Rust version is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. The protocol has to match before you can join, and Steam does the updating.
How reliable is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, and is it up?
Offline now for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, last seen 13 days 7 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 15 October 2026.
Which location does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run from?
No region is published by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 122.40.171.64:28065 is its address.
Rules, settings, map
Which settings and rules does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run?
You will not find a gather rate in the string BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Wipe data
When does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION wipe, and how often?
The record for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 13 days 8 hours ago.
On BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION appear among Rust Data lists and filters?
The Rust Data lists that BUNDANG_FULL_CORRIDOR_V8_VERIFICATION fits are: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
Read by the game's server browser, the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $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.
Connecting
How can I connect to BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The manual route: launch Rust, F1, then client.connect 122.40.171.64:28065. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.