BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Offline 122.40.171.64:28065 checked 12d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
too few wipes seen yetNot 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 21:52 UTC13d ago | 0° | – | 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
Its recent wipes drew an average peak of 0 players. 0 hours into the latest wipe, player numbers topped out.
What is the wipe schedule on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The record of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION's wipes is not yet long enough to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 13 days ago.
Player counts
How busy is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The last time BUNDANG_FULL_CORRIDOR_V8_VERIFICATION was seen was 12 days 23 hours ago, and it is offline now.
How does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION rank against other Rust servers?
Ranked #15,101 on seven-day player hours, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is in the top 70% of all ranked servers.
Settings and rules
What are the rules and settings on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The name BUNDANG_FULL_CORRIDOR_V8_VERIFICATION does not specify a gather rate. 8 players is the default group size, and that is the limit here. The server runs survival, standard play: gathering, building and raiding. You can fight other players and raid their bases. You will find it under Community in the server browser; it is a community server. VAC is on, which is Valve's anti-cheat.
Location and uptime
Which version of Rust does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run?
The build on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is Rust network protocol 2634 and build 167781, running on Windows. Steam updates your game for you, and the protocol has to match for you to join.
Is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION online, and how reliable is it?
Offline at the moment: BUNDANG_FULL_CORRIDOR_V8_VERIFICATION was last seen 12 days 23 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. Rust Heatmap has had it on record since 15 October 2026.
Where is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION located?
No region is published by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. You can reach it at 122.40.171.64:28065.
Tags
Which Rust Heatmap lists and filters include BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The Rust Heatmap lists that BUNDANG_FULL_CORRIDOR_V8_VERIFICATION fits are: Best Rust community servers. These are the filters that return it on the list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
What do the server tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION mean?
The game's server browser reads the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION publishes: gmrust (Game mode): Rust survival, standard rules; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): Your game must match protocol 2634 to get in; cs167781 (Build): This build is 167781; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
Connect
How do I join BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
To join by console, open it with F1 in Rust and enter client.connect 122.40.171.64:28065. Or press Launch Rust on this page, which connects you through Steam.