Station XX-15101 · no signal
BUNDANG_FULL_CORRIDOR_V8_VERIFICATION
Offline 122.40.171.64:28065 checked 12d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,101
- top 70%
- Last wipe
- 12d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 slots
- Motion · 24 h
- M –not enough readings
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.
- wipe-day peak
- 0players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 21:52 UTC12d ago | M0.0■steady | 0 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which settings and rules apply on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
The name of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION right now?
No players are recorded on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION at this moment; it is offline, and the last sighting was 12 days 13 hours ago.
How does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION rank against other Rust servers?
On player hours for the past week, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION sits at #15,101, which puts it inside the top 70% of every ranked server.
Server facts
How reliably does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION stay online?
No contact with BUNDANG_FULL_CORRIDOR_V8_VERIFICATION right now, and the last recorded contact was 12 days 13 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 15 October 2026.
Which region does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run from?
Nothing about a region comes from BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 122.40.171.64:28065.
Which Rust version is BUNDANG_FULL_CORRIDOR_V8_VERIFICATION running?
On Windows, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION runs Rust network protocol 2634 and build 167781. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION run its wipes?
Too few wipes of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 12 days 13 hours.
Lists and tags
What do the server tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION mean?
The game's server browser reads the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION publishes: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION appear?
The Rust Server Trends lists that take in BUNDANG_FULL_CORRIDOR_V8_VERIFICATION are: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?
To join, enter client.connect 122.40.171.64:28065 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.