Statistical profileOffline
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
122.40.171.64:28065 checked 13d ago
Connect to this server
1. Main points
Players now
0/ 1
0% full
7-day average
0
peak –
Rank
#15,101
top 70%
Last wipe
13d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 1 slots.
- It ranks #15,101 of all ranked servers, the top 70%, on player hours over the last seven days.
- Its current map went up 13d ago.
2. Players
Figure 1: Players on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo 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 peak
0
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 21:52 UTC13d ago | 0 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Table 2: The world
As the server publishes it
| Map | Custom Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 549 on average | 135 / 250 |
| Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 120 / 200 |
| Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 14 / 250 |
| Rustoria.co - EU Main | EU · groups of 16+ · weekly · 284 on average | 17 / 250 |
| Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 13 / 100 |
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 249 on average | 37 / 200 |
10. Quick answers
From the figures on this page.
Wipe records
When does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION wipe, and how often?
Too few wipes of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION are on record to establish its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 13 days 6 hours have passed since this world was made.
On BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, what happens on wipe day?
An average of 0 players attended at peak across recent wipes. On the latest wipe, 0 hours passed before the crowd peaked.
Server record
Is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION up, and how well has it held up?
Last seen 13 days 6 hours ago, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is offline in this release. A total of 0 of 168 hours were up over 7 full days, which is 0% of the time. The first sighting of it by Rust Census was on 15 October 2026.
Which location does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run from?
No region is given by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 122.40.171.64:28065 is its address.
What version of Rust has been recorded on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
This release lists BUNDANG_FULL_CORRIDOR_V8_VERIFICATION on Rust network protocol 2634 and build 167781, running on Windows. The same protocol is required for your game to join, and Steam updates it for you.
Player figures
What are the current player figures for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
At this release BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is offline, having last been seen 13 days 6 hours ago.
In the rankings of Rust servers, where is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION placed?
The rank for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is #15,101 on seven-day player hours, in the top 70% of ranked servers.
Tags, lists
Which Rust Census filters and lists cover BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The Rust Census lists that BUNDANG_FULL_CORRIDOR_V8_VERIFICATION fits are: Community servers. Under these filters it comes up 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.
The tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: what do they indicate?
These are the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION publishes for the game's server browser to read: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp1 (Max players): Slots: 1; ts8 (Group limit): This is the game default: 8 to a team; v2634 (Protocol): Your game must run protocol 2634 to join; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): No region code is set. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Map and rules
How is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION configured, and what rules does it keep?
No gather rate is recorded for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION in its name. The default applies: groups are capped at 8 players. survival is the game mode recorded, the standard game: gather, build, raid. Raiding and player combat are permitted. It appears under Community in the server browser. The server runs VAC, Valve's anti-cheat.
Join details
What is the way to join BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
You can open the console in Rust with F1 and enter client.connect 122.40.171.64:28065; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp1 | Max players Slots: 1. |
ts8 | Group limit This is the game default: 8 to a team. |
v2634 | Protocol Your game must run protocol 2634 to join. |
cs167781 | Build The server runs game build 167781. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code No region code is set. |
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.