Live coverage · Rust server
Offline BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is not on the server list right now. The figures below are from when it was last seen, 13d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
The current map
Thursday 15 October 2026, 21:52 UTC
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.
At their busiest, its recent wipes averaged 0 players. Peak population on the latest wipe came 0 hours after it.
Too few wipes are recorded for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION to establish a pattern. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. The world you are playing on was built 13 days 12 hours.
These are the Rust Live Stats lists BUNDANG_FULL_CORRIDOR_V8_VERIFICATION fits: Live Rust community servers. You will find it on the server list under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
These are the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION makes public: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): You need protocol 2634 on your game to get in; cs167781 (Build): Build: 167781; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is not online at the moment, having last been seen 13 days 12 hours ago.
Player hours over seven days put BUNDANG_FULL_CORRIDOR_V8_VERIFICATION at #15,101, in the top 70% of all ranked servers.
No gather rate appears in the name BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. Fighting and raiding between players are allowed. You find it under Community in the server browser. VAC is enabled: Valve's anti-cheat.
There is no region from BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 122.40.171.64:28065.
Rust network protocol 2634 and build 167781 on Windows is what BUNDANG_FULL_CORRIDOR_V8_VERIFICATION runs. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is down, last seen 13 days 12 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. On 15 October 2026, Rust Live Stats saw it for the first time.
Enter client.connect 122.40.171.64:28065 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.