BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Offline 122.40.171.64:28065 checked 13d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
Wipes
newest first| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 320/375
- 203/250
- 35/250
- 24/250
- 52/100
- 65/200
Quick answers
from the figures on this pageWipe timing
What happens on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION when wipe day comes?
An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.
How often does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION wipe, and when?
To tell the rhythm of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 13 days 2 hours ago.
Tags
How should you read the tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
These are the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION appear in Rust Metrics lists and filters?
Rust Metrics lists featuring BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Population
What position does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION hold among Rust servers?
Player hours over seven days put BUNDANG_FULL_CORRIDOR_V8_VERIFICATION at #15,101, in the top 70% of all ranked servers.
How full does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION get?
Status for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: offline. Last seen 13 days 1 hours ago.
Operator and location
Which location does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run from?
No region comes from BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 122.40.171.64:28065.
What Rust version is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Matching protocol is required to join. Let Steam update your game.
How reliable is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, and is it online now?
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION reports offline. The last reading came 13 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 15 October 2026, recorded by Rust Metrics.
Settings and map
How is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION configured, and what rules are in force?
Check: gather rate. The name BUNDANG_FULL_CORRIDOR_V8_VERIFICATION does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
Join
How can you get onto BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
To join: start Rust, press F1 and type client.connect 122.40.171.64:28065. Or press Launch Rust here and Steam opens the game and connects you.