BND15101
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Offline 122.40.171.64:28065 checked 13d ago
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
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.
-
01COMPlayers 342/375
-
02COMPlayers 230/250
-
03COMPlayers 36/250
-
04COMPlayers 29/250
-
05COMPlayers 58/100
-
06COMPlayers 79/200
Quick answers
From the figures on this page.
Filters
Which lists and filters on Rust Tracker show BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
On Rust Tracker, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION sits in these lists: Community servers, no tags. These filters surface it on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The game's server browser reads these tags from BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: gmrust (Game mode): Rust survival, standard mode; mp1 (Max players): 1 slots on this server; ts8 (Group limit): Team limit is 8, the game default; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): This server runs game build 167781; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Schedule
What should you expect on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION when wipe day lands?
Recent wipes averaged a peak of 0 players. The peak on the latest wipe came 0 hours after it.
On what schedule does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION wipe?
Too few wipes on record for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. This world has been running 13 days 1 hours.
Server Details
What is the uptime on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, and is it online?
Offline: BUNDANG_FULL_CORRIDOR_V8_VERIFICATION confirmed offline, last seen 13 days 1 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. The first sighting by Rust Tracker was 15 October 2026.
Which Rust build is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION running?
Rust network protocol 2634 and build 167781 on Windows is what BUNDANG_FULL_CORRIDOR_V8_VERIFICATION runs. Steam updates it for you; your game must share the protocol to join.
Where does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION sit?
Region: none published by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 122.40.171.64:28065.
Population
How many players are on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION right now?
Last seen 13 days 1 hours ago; BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is offline at present.
How does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION compare in the rankings?
Seven-day player hours put BUNDANG_FULL_CORRIDOR_V8_VERIFICATION at #15,101, within the top 70% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The name of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION carries no gather rate. Up to 8 players per group, the game's default. survival is the game mode, gather, build and raid: the standard game. Players can raid and fight each other here. A community server: the server browser lists it under Community. VAC is on, Valve's anti-cheat.
Connect
What is the way to join BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
To connect: start Rust, press F1, enter client.connect 122.40.171.64:28065 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
Server tags
What each one means.
Published as mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
mp1
ts8
v2634
cs167781
ptrak
$r?
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.