RUST METRICSFlight deck · live data
Data live Servers11,698 Players65,296 Populated3,536 Fresh wipes 3 h114 Scan5 min
‹ All servers122.40.171.64:28045
Offline Full Queue Fresh wipe Wipe due No query

BUNDANG_SOURCE_RECOVERY_LAND_TEST

Offline 122.40.171.64:28045 checked 12d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,164top 70%
Last wipe12d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

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.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

How often does BUNDANG_SOURCE_RECOVERY_LAND_TEST wipe, and when?

Its rhythm cannot be told from the wipes of BUNDANG_SOURCE_RECOVERY_LAND_TEST on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 12 days 23 hours ago the current world was made.

Tags

Which tags does BUNDANG_SOURCE_RECOVERY_LAND_TEST carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from BUNDANG_SOURCE_RECOVERY_LAND_TEST. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show BUNDANG_SOURCE_RECOVERY_LAND_TEST?

On Rust Metrics, BUNDANG_SOURCE_RECOVERY_LAND_TEST sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does BUNDANG_SOURCE_RECOVERY_LAND_TEST hold among Rust servers?

Ranking for BUNDANG_SOURCE_RECOVERY_LAND_TEST: #15,164 on seven-day player hours, top 70% of all ranked servers.

What is the population on BUNDANG_SOURCE_RECOVERY_LAND_TEST?

Reading for BUNDANG_SOURCE_RECOVERY_LAND_TEST: offline at this moment; last seen 12 days 22 hours ago.

Operator and location

Where does BUNDANG_SOURCE_RECOVERY_LAND_TEST sit?

No region tag on BUNDANG_SOURCE_RECOVERY_LAND_TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 122.40.171.64:28045.

What Rust version is BUNDANG_SOURCE_RECOVERY_LAND_TEST on?

Rust network protocol 2634 and build 167781 on Windows is the build BUNDANG_SOURCE_RECOVERY_LAND_TEST runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is BUNDANG_SOURCE_RECOVERY_LAND_TEST, and is it online now?

Check: connection. BUNDANG_SOURCE_RECOVERY_LAND_TEST is offline at this moment. Last contact was 12 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 October 2026.

Settings and map

How is BUNDANG_SOURCE_RECOVERY_LAND_TEST configured, and what rules are in force?

Check: gather rate. The name BUNDANG_SOURCE_RECOVERY_LAND_TEST does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Join

How can you get onto BUNDANG_SOURCE_RECOVERY_LAND_TEST?

Press F1 in Rust and enter client.connect 122.40.171.64:28045. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.