RUST METRICSFlight deck · live data
Data live Servers11,693 Players37,293 Populated2,927 Fresh wipes 3 h93 Scan5 min
‹ All servers122.40.171.64:28035
Offline Full Queue Fresh wipe Wipe due No query

BUNDANG_LOCAL_TILEFIX

Offline 122.40.171.64:28035 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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 10:21 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 should you expect from wipe day on BUNDANG_LOCAL_TILEFIX?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does BUNDANG_LOCAL_TILEFIX wipe, and when?

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

Tag meanings

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

Tags published by BUNDANG_LOCAL_TILEFIX, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does BUNDANG_LOCAL_TILEFIX appear in Rust Metrics lists and filters?

Rust Metrics lists featuring BUNDANG_LOCAL_TILEFIX: 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.

Population

Where does BUNDANG_LOCAL_TILEFIX sit in the rankings?

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

What is the population on BUNDANG_LOCAL_TILEFIX?

BUNDANG_LOCAL_TILEFIX is not responding; status offline, last seen 12 days 16 hours ago.

Server details

Where does BUNDANG_LOCAL_TILEFIX sit?

No region comes from BUNDANG_LOCAL_TILEFIX. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 122.40.171.64:28035.

What Rust version is BUNDANG_LOCAL_TILEFIX on?

Rust network protocol 2634 and build 167781 on Windows is the build BUNDANG_LOCAL_TILEFIX runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is BUNDANG_LOCAL_TILEFIX, and is it online now?

Check: connection. BUNDANG_LOCAL_TILEFIX is offline at this moment. Last contact was 12 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 October 2026, recorded by Rust Metrics.

Map and rules

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

Check: gather rate. The name BUNDANG_LOCAL_TILEFIX does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Connection

What do you do to join BUNDANG_LOCAL_TILEFIX?

Check: join. Open Rust, press F1, then enter client.connect 122.40.171.64:28035. 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 Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.