BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Offline 122.40.171.64:28065 checked 13d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server 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.
Rank
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
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
| 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.
Quick answers
Population
How does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION rank against other Rust servers?
Over the past week it ranks #15,101 for player hours, which puts BUNDANG_FULL_CORRIDOR_V8_VERIFICATION in the top 70% of all ranked servers.
How busy is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
At this count BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is offline, with its last sighting 13 days 2 hours ago.
Lists and tags
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): The game mode is standard Rust survival; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
These Rust Population lists include BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: Community servers, field-listed. These are the filters it appears under when you browse 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.
Wipe schedule
What does wipe day look like on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The busiest point of its recent wipes averaged 0 players. The crowd on the latest wipe peaked 0 hours in.
What is the wipe schedule on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
Too few wipes are on record for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 13 days 2 hours ago, that is how long the current world has stood.
Settings
What are the rules and settings on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The name tells you nothing about gather rates: BUNDANG_FULL_CORRIDOR_V8_VERIFICATION states none. Eight players per group is the default, and it applies here. This server runs survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. The server browser lists it under Community, as a community server. The anti-cheat VAC from Valve is enabled.
About the server
Which version of Rust does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run?
On Windows, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION runs Rust network protocol 2634 and build 167781. Your game needs the same protocol to join; Steam takes care of updating it.
Is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION online, and how reliable is it?
Offline at the moment, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION was last seen 13 days 2 hours ago. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. The first sighting by Rust Population was on 15 October 2026.
Where is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION located?
A region is not published by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Rust Population does not look up where the machine stands; it shows where the server says it is. You will find it at 122.40.171.64:28065.
Getting in
How do I join BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
Open the console with F1 in Rust and enter client.connect 122.40.171.64:28065. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.