RUST METRICSFlight deck · live data
Data live Servers11,700 Players44,565 Populated3,103 Fresh wipes 3 h103 Scan5 min
‹ All servers122.40.171.64:28025
Offline Full Queue Fresh wipe Wipe due No query

BUNDANG_LOCAL_SPAWNFIX

Offline 122.40.171.64:28025 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,114top 70%
Last wipe13d agono schedule published
Next wipe–too few wipes 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 Oct17 Oct18 Oct20 Oct21 Oct23 Oct

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

PLAN

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 peak1players, 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 1, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 09:59 UTC13d ago 1 – 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe schedule

What happens on BUNDANG_LOCAL_SPAWNFIX when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in.

What wipe timing does BUNDANG_LOCAL_SPAWNFIX follow?

The rhythm of BUNDANG_LOCAL_SPAWNFIX's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 13 days 15 hours ago.

Tag meanings

How should you read the tags on BUNDANG_LOCAL_SPAWNFIX?

These are the tags BUNDANG_LOCAL_SPAWNFIX publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; 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): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does BUNDANG_LOCAL_SPAWNFIX appear in Rust Metrics lists and filters?

On Rust Metrics, BUNDANG_LOCAL_SPAWNFIX sits in these lists: Rust community servers: live readings. These filters bring it 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.

Player count

What position does BUNDANG_LOCAL_SPAWNFIX hold among Rust servers?

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

How full does BUNDANG_LOCAL_SPAWNFIX get?

BUNDANG_LOCAL_SPAWNFIX is not responding; status offline, last seen 12 days 15 hours ago.

Server details

Which location does BUNDANG_LOCAL_SPAWNFIX run from?

No region comes from BUNDANG_LOCAL_SPAWNFIX. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 122.40.171.64:28025.

What Rust version is BUNDANG_LOCAL_SPAWNFIX on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by BUNDANG_LOCAL_SPAWNFIX. Matching protocol is required to join. Let Steam update your game.

How reliable is BUNDANG_LOCAL_SPAWNFIX, and is it online now?

Reading: offline. BUNDANG_LOCAL_SPAWNFIX last answered 12 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 15 October 2026.

Map and rules

What rules does BUNDANG_LOCAL_SPAWNFIX enforce, and what are its settings?

Reading the name gives no gather rate for BUNDANG_LOCAL_SPAWNFIX. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Join

How do you connect to BUNDANG_LOCAL_SPAWNFIX?

Check: join. Open Rust, press F1, then enter client.connect 122.40.171.64:28025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
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 The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for 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.