This server publishes no banner
Exhibit no. 15,101Acc. 2026.15101
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Rust server · in the archive since 15 October 2026
Offline 122.40.171.64:28065 checked 13d ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
15 Oct Last seen 15 Oct21:52
a wipe on recordthe monthly force wipeexpectedlast seen, 15 Oct 2026, 22:10 UTCAll times UTC.
The record of each wipe
-
Thu 15 Oct 202621:52 UTC13d ago
- Peak
- 0
- Crowd
- –
- Lasted
- running
- Players before
- 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.
The rhythm
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.
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.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
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
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags and filters
What do the server tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION mean?
You can see the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION publishes, read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): 1 slots are set on this server; ts8 (Group limit): The default cap of 8 per team applies here; v2634 (Protocol): The server runs game protocol 2634; matching it is required to join; cs167781 (Build): This server runs game build 167781; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The region code field is empty. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.
Which Rust Server History lists and filters include BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
These Rust Server History lists include BUNDANG_FULL_CORRIDOR_V8_VERIFICATION: Rust community servers. It appears under these filters 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 record
Which version of Rust does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run?
The recorded build for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is Rust network protocol 2634 and build 167781 on Windows. Steam updates your game for you; joining needs the same protocol.
Is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION online, and how reliable is it?
The record shows BUNDANG_FULL_CORRIDOR_V8_VERIFICATION offline at this moment, last seen 13 days 5 hours ago. Of 168 hours in the last 7 full days, 0 were up: 0% of the time. 15 October 2026 is when Rust Server History first saw it.
Where is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION located?
There is no region published by BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Rust Server History does not look up where the machine stands; it shows where a server says it is. You will find it at 122.40.171.64:28065.
Wipe record
What does wipe day look like on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
An average peak of 0 players was drawn by its recent wipes. On the latest wipe, 0 hours after the wipe, the crowd peaked.
What is the wipe schedule on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
Its rhythm is not yet clear: too few of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION's wipes are on record. The monthly force wipe comes next on Thursday 5 November at 19:00 UTC, and every Rust server wipes then. Made 13 days 6 hours ago, the current world is what it runs now.
Population
How does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION rank against other Rust servers?
Over seven days of player hours, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION ranks #15,101, inside the top 70% of all ranked servers.
How busy is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is offline at present, having last been seen 13 days 5 hours ago.
Rules, map
What are the rules and settings on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
No gather rate is stated in the name of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. The limit of 8 players per group is the game's default. Recorded as survival, with this note: gather, build, raid: the standard game. You may fight and raid other players. The server browser lists it under Community, as a community server. The anti-cheat VAC from Valve is active.
Joining the server
How do I join BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
Enter client.connect 122.40.171.64:28065 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you.
The label explained
Server tags
What each tag this server publishes 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.