Skip to the content
Dive report

BUNDANG_FULL_CORRIDOR_V8_VERIFICATION

Offline 122.40.171.64:28065 checked 2d ago

Drop in
0/ 1 players now 0% full
07-day averagepeak –
#15,843ranktop 72%
2d agolast wipeno schedule published
–next wipetoo few wipes seen yet

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k15 Oct16 Oct17 Oct18 Oct

Top 72% of all ranked servers. Ranked on player hours over the last seven days.

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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 21:52 UTC2d 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.

Neighbouring dive spots

Similar servers

the same kind of game, then region, group limit, rate and wipes

From the figures on this page

Quick answers

Tags and search

Where does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION appear in Rust Going Deep lists and filters?

These Rust Going Deep lists include BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

What's the meaning of the tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

The server browser shows these tags for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): It's on build 167781; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.

Server details

Where can you find BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

No region comes from BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 122.40.171.64:28065.

What's the uptime like for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

Right now BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is offline, having last been seen 2 days 10 hours ago. In the last full 2 days, 0 of 48 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 15 October 2026.

What Rust version is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION on?

Rust network protocol 2634 and build 167781 is what BUNDANG_FULL_CORRIDOR_V8_VERIFICATION runs, on Windows. The protocol must match to join; Steam will update your game.

Wipe schedule

When does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION wipe?

BUNDANG_FULL_CORRIDOR_V8_VERIFICATION's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. The world you are on now was created 2 days 10 hours.

What can you expect on wipe day at BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

The average peak across recent wipes is 0 players. The peak crowd on the latest wipe came 0 hours in.

Map and rules

What settings and rules have been applied to BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

Its name does not state a gather rate for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. It sits under Community in the server browser: a community server. VAC is on: Valve's anti-cheat is active.

Player count

Is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION busy?

BUNDANG_FULL_CORRIDOR_V8_VERIFICATION was last seen 2 days 10 hours ago and is offline as you read this. Across the last seven days, the typical count has been 0 players.

Where does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION sit in the rankings?

For player hours in the last seven days, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION ranks #15,843, within the top 72% of ranked servers.

Getting in

What's the way to join BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 122.40.171.64:28065.

What each one means

Server tags

Published as mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode This is the standard Rust survival experience.
mp1
Max players The slot count is 1.
ts8
Group limit Teams cap at 8, which is the game default.
v2634
Protocol To join, your game has to be on protocol 2634.
cs167781
Build It's on build 167781.
ptrak
Networking The network layer is RakNet, Rust's default.
$r?
Region code It has no region code.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.