Rust Server TrendsSeismic network · station log
Recording Stations11,652 Players32,618 Active2,799 Wipes · 3 h77 48 h

Station XX-15114 · no signal

BUNDANG_LOCAL_SPAWNFIX

Offline 122.40.171.64:28025 checked 12d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,114
top 70%
Last wipe
13d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15114 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 1 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 peak
1players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 15 Oct, 09:59 UTC13d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 549 on average
147/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
116/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
13/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 284 on average
18/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
13/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 249 on average
29/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which settings and rules apply on BUNDANG_LOCAL_SPAWNFIX?

No gather rate appears in the name of BUNDANG_LOCAL_SPAWNFIX. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on BUNDANG_LOCAL_SPAWNFIX?

No players are recorded on BUNDANG_LOCAL_SPAWNFIX at this moment; it is offline, and the last sighting was 12 days 18 hours ago.

How does BUNDANG_LOCAL_SPAWNFIX rank against other Rust servers?

On player hours for the past week, BUNDANG_LOCAL_SPAWNFIX sits at #15,114, which puts it inside the top 70% of every ranked server.

Server details

How reliably does BUNDANG_LOCAL_SPAWNFIX stay online?

No contact with BUNDANG_LOCAL_SPAWNFIX right now, and the last recorded contact was 12 days 18 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 15 October 2026 is when Rust Server Trends first recorded it.

Where in the world is BUNDANG_LOCAL_SPAWNFIX hosted?

No region is published by BUNDANG_LOCAL_SPAWNFIX. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 122.40.171.64:28025.

What build of Rust does BUNDANG_LOCAL_SPAWNFIX use?

BUNDANG_LOCAL_SPAWNFIX is running Rust network protocol 2634 and build 167781 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on BUNDANG_LOCAL_SPAWNFIX?

On average, the busiest point of its recent wipes drew 1 players. 1 hours into the latest wipe, the crowd reached its peak.

On what timetable does BUNDANG_LOCAL_SPAWNFIX run its wipes?

On record so far are too few of BUNDANG_LOCAL_SPAWNFIX's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 13 days 18 hours.

Server tags

What do the server tags on BUNDANG_LOCAL_SPAWNFIX mean?

Tags published by BUNDANG_LOCAL_SPAWNFIX and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does BUNDANG_LOCAL_SPAWNFIX appear?

The Rust Server Trends lists that take in BUNDANG_LOCAL_SPAWNFIX are: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Join the server

What steps get you onto BUNDANG_LOCAL_SPAWNFIX?

To join, enter client.connect 122.40.171.64:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp1
Max players 1 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build The game build is 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.