Rust Data LabData lab · live
Live readings Servers11,803 Players71,182 Populated3,639 Fresh wipes · 3h205 Sampled every 5 min

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

BUNDANG_LOCAL_TILEFIX

Offline 122.40.171.64:28035 checked 13d ago

Join the experiment
Atomic mass · players now 0/ 1 0% full Room to join
7-day average0peak –
Rank · atomic number#15,114top 70%
Last wipe14d 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 Oct17 Oct18 Oct20 Oct21 Oct23 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 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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 10:21 UTC14d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 522
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 513 on average 522/ 550
  2. 2 Ru Rustoria.co - … 438
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average 438/ 450
  3. 3 Ru Rusty Moose |E… 60
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 60/ 250
  4. 4 Ru Rustoria.co - … 66
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average 66/ 250
  5. 5 Ru Rustafied.com … 53
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 53/ 100
  6. 6 Ru Rustoria.co - … 164
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 238 on average 164/ 200

Quick answers

from the figures on this page

Map and rules

What settings and rules apply on BUNDANG_LOCAL_TILEFIX?

The name of BUNDANG_LOCAL_TILEFIX carries no gather rate. Eight players per group is the limit, the game's default. survival is the game mode, raiding, building and gathering: the standard game. You can fight other players and raid them. You will find it under Community in the server browser. The VAC anti-cheat from Valve is enabled.

Server facts

In what location does BUNDANG_LOCAL_TILEFIX sit?

Nothing about a region is published by BUNDANG_LOCAL_TILEFIX. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 122.40.171.64:28035.

Which Rust version is BUNDANG_LOCAL_TILEFIX on?

Rust network protocol 2634 and build 167781 on Windows is what BUNDANG_LOCAL_TILEFIX uses. Your game needs to match the protocol to join, and Steam updates it automatically.

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

BUNDANG_LOCAL_TILEFIX is not online at the moment; the last sighting was 13 days 3 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. On 15 October 2026, Rust Data Lab saw it for the first time.

Wipe schedule

How often does a wipe happen on BUNDANG_LOCAL_TILEFIX, and at what time?

The record holds too few of BUNDANG_LOCAL_TILEFIX's wipes to show its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 14 days 1 hours ago.

On BUNDANG_LOCAL_TILEFIX, what happens when wipe day arrives?

Recent wipes on average reached 1 players at their busiest. Peak numbers on the latest wipe came 0 hours in.

Lists and tags

How should you read the tags on BUNDANG_LOCAL_TILEFIX?

The game's server browser reads the tags BUNDANG_LOCAL_TILEFIX publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): It has 1 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): It runs build 167781; ptrak (Networking): This runs on RakNet, the standard layer; $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_LOCAL_TILEFIX appear in?

You will find BUNDANG_LOCAL_TILEFIX on the following Rust Data Lab lists: Rust community servers, measured. 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.

Population

What position does BUNDANG_LOCAL_TILEFIX hold among Rust servers?

BUNDANG_LOCAL_TILEFIX sits at #15,114 for seven-day player hours, placing it in the top 70% of ranked servers.

What does the current player count on BUNDANG_LOCAL_TILEFIX tell you?

The last recorded sighting of BUNDANG_LOCAL_TILEFIX was 13 days 3 hours ago, and it is offline now.

How to join

What is the way to join BUNDANG_LOCAL_TILEFIX?

In Rust, press F1 and enter client.connect 122.40.171.64:28035. Or click Launch Rust here to open Rust via Steam and connect automatically.

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 It has 1 slots.
ts8
Group limit Teams cap at 8, which is the game default.
v2634
Protocol To join, your game must match protocol 2634.
cs167781
Build It runs build 167781.
ptrak
Networking This runs on RakNet, the standard layer.
$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.