BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 13d ago · 122.40.171.64:28065
Abstract
We describe the public Rust server BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, reached at 122.40.171.64:28065. It is offline at the last check, against a seven-day mean of 01. It ranks #15,101 of all servers, the top 70%. It last wiped 13d ago.
Keywordsrust server
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 70% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: 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.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 0 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 15 Oct, 21:5213d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 122.40.171.64:28065 |
|---|---|
| Region | – |
| Max players | 1 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 15 Oct 2026, 21:52 UTC |
| Hostname | – |
| First seen | 15 Oct 2026 |
| Map | Custom Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are unmodded rust community servers [2] and next Rust wipe times [3].
| Server | Players |
|---|---|
| Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 560 on average | 246/275 |
| Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average | 175/200 |
| Rusty Moose |EU Main|EU · groups of 12+ · weekly · 292 on average | 32/250 |
| Rustoria.co - EU MainEU · groups of 16+ · weekly · 291 on average | 17/250 |
| Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average | 41/100 |
| Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average | 53/200 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1What location does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION have?
No region is published by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 122.40.171.64:28065.
A.2What is the reliability of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, and is it online?
Right now, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is offline, and the last time it was seen was 13 days 2 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first observed on 15 October 2026 by Rust Statistics.
A.3What version of Rust is run on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The version of Rust on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is network protocol 2634 and build 167781, and the operating system is Windows. To join, your game must use the same protocol; Steam handles the update for you.
Wipe schedule
A.4On what cycle does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION wipe?
The record of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 13 days 2 hours have passed since the current world was generated.
A.5How would you describe wipe day on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The average busiest point of recent wipes was 0 players. The peak on the latest wipe came 0 hours after it began.
Population
A.6What is the rank of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION among Rust servers?
Ranked by player hours across seven days, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION holds #15,101, in the top 70% of all ranked servers.
A.7At what level does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION operate in terms of players?
The last recorded sighting of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION was 13 days 2 hours ago; it is offline now.
Tags and filters
A.8What do the tags associated with BUNDANG_FULL_CORRIDOR_V8_VERIFICATION signify?
gmrust (Game mode): Survival on standard Rust rules; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset: these are the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.9Where can BUNDANG_FULL_CORRIDOR_V8_VERIFICATION be found among the Rust Statistics lists and filters?
Rust community servers, measured are the Rust Statistics lists that BUNDANG_FULL_CORRIDOR_V8_VERIFICATION fits. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules, settings, map
A.10Under what rules and settings does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION operate?
The name of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION states no gather rate. The group cap is 8 players, which is the default in the game. survival is the game mode here; the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
How to join
A.11What is the process for joining BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
Enter client.connect 122.40.171.64:28065 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.
Appendix BServer tags
What each of the server's tags means. Published as mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp1 | Max players. 1 slots are available. |
ts8 | Group limit. Teams are limited to 8, as the game defaults. |
v2634 | Protocol. The game protocol is 2634; your client must match it to join. |
cs167781 | Build. The game build is 167781. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. The region code is unset. |
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.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Unmodded rust community servers. ruststatistics.org/top-rust-community-servers.
- [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.