Rust Data LabData lab · live
Live readings Servers11,680 Players38,014 Populated2,926 Fresh wipes · 3h94 Sampled every 5 min

Element card · group Community · atomic number 15,101, its rank

BUNDANG_FULL_CORRIDOR_V8_VERIFICATION

Offline 122.40.171.64:28065 checked 13d ago

Join the experiment
Atomic mass · players now 0/ 1 0% full Room to join
7-day average0peak –
Rank · atomic number#15,101top 70%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
This server has not answered a direct query in the last 48 hours.

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k15 Oct16 Oct18 Oct19 Oct21 Oct22 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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
  1. 1 Ru Rusty Moose |E… 165
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 560 on average 165/ 250
  2. 2 Ru Rustoria.co - … 116
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 116/ 200
  3. 3 Ru Rusty Moose |E… 18
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 18/ 250
  4. 4 Ru Rustoria.co - … 14
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 288 on average 14/ 250
  5. 5 Ru Rustafied.com … 17
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average 17/ 100
  6. 6 Ru Rustoria.co - … 25
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 250 on average 25/ 200

Quick answers

from the figures on this page

Map and rules

What rules has BUNDANG_FULL_CORRIDOR_V8_VERIFICATION set, and what settings are in force?

No gather rate appears in the name of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. Groups top out at 8 players, the default for the game. survival is the game mode, gather, build and raid, as in the standard game. You can fight other players and raid them. It appears under Community in the server browser. Anti-cheat is on: Valve's VAC.

Server details

In what location does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION sit?

There is no region on record for BUNDANG_FULL_CORRIDOR_V8_VERIFICATION. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. 122.40.171.64:28065 is the address it uses.

What Rust version does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION currently run?

On Windows, BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is running Rust network protocol 2634 and build 167781. The protocol must match for you to join; Steam will update your game.

Does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION stay up, and how reliable is its uptime?

BUNDANG_FULL_CORRIDOR_V8_VERIFICATION is not online at the moment; the last sighting was 13 days 4 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. On 15 October 2026, Rust Data Lab saw it for the first time.

Wipes and resets

What is the wiping pattern on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

The record holds too few of BUNDANG_FULL_CORRIDOR_V8_VERIFICATION's wipes to show its rhythm. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. Counting back, the current world began 13 days 4 hours ago.

On BUNDANG_FULL_CORRIDOR_V8_VERIFICATION, what happens when wipe day arrives?

At their busiest, recent wipes averaged 0 players. The latest wipe's peak fell 0 hours after it began.

Where it appears

Which meanings sit behind the tags on BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

These are the tags BUNDANG_FULL_CORRIDOR_V8_VERIFICATION makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): Player slots: 1; ts8 (Group limit): 8 per team, the default the game ships with; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION appear in?

The Rust Data Lab lists that include BUNDANG_FULL_CORRIDOR_V8_VERIFICATION are: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player counts

Against other Rust servers, where does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION place?

The seven-day player-hours table has BUNDANG_FULL_CORRIDOR_V8_VERIFICATION at #15,101, in the top 70% of ranked servers.

How many players does BUNDANG_FULL_CORRIDOR_V8_VERIFICATION have at the moment?

No live signal from BUNDANG_FULL_CORRIDOR_V8_VERIFICATION right now, which was last seen 13 days 4 hours ago.

How to join

What steps get you onto BUNDANG_FULL_CORRIDOR_V8_VERIFICATION?

You can connect by pressing F1 in Rust and entering client.connect 122.40.171.64:28065, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival in the standard Rust style.
mp1
Max players Player slots: 1.
ts8
Group limit 8 per team, the default the game ships with.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs167781
Build Build number: 167781.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

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.