Rust Server TrendsSeismic network · station log
Recording Stations11,691 Players35,842 Active2,916 Wipes · 3 h97 48 h

Station XX-13570 · no signal

DaGaHa_Build

Offline 147.147.153.164:28015 checked 17d ago

Connect
Players now
1/ 50
2% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,570
top 61%
Last wipe
17d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-13570 · 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
1of 50 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
15k10k15k20k11 Oct12 Oct14 Oct15 Oct17 Oct18 Oct

Top 61% 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

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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 11 Oct, 13:27 UTC17d 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 · 555 on average
164/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
96/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
15/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 286 on average
17/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
12/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 250 on average
17/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on DaGaHa_Build?

DaGaHa_Build uses a procedural map, which the game generates.

Which settings and rules apply on DaGaHa_Build?

No gather rate appears in the name of DaGaHa_Build. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on DaGaHa_Build?

A reading taken now finds DaGaHa_Build offline; the most recent activity was 17 days 11 hours ago.

How does DaGaHa_Build rank against other Rust servers?

On player hours for the past week, DaGaHa_Build sits at #13,570, which puts it inside the top 61% of every ranked server.

Operator and location

How reliably does DaGaHa_Build stay online?

As recorded now, DaGaHa_Build is not reachable, the last contact having been 17 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 11 October 2026 is when Rust Server Trends first recorded it.

Where in the world is DaGaHa_Build hosted?

No region is published by DaGaHa_Build. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 147.147.153.164:28015.

Which Rust version is DaGaHa_Build running?

Rust network protocol 2635 and build 167528 on Windows is what DaGaHa_Build runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on DaGaHa_Build?

1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.

How often does DaGaHa_Build wipe, and on which days?

Too few wipes of DaGaHa_Build are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 17 days 13 hours is how long the current world has been running.

Server tags

What do the server tags on DaGaHa_Build mean?

The game's server browser reads the tags DaGaHa_Build publishes: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs167528 (Build): Game build: 167528; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does DaGaHa_Build appear?

You will find DaGaHa_Build on the following Rust Server Trends lists: Rust build and creative servers, live and Rust community servers without the side modes. 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.

Join the server

What steps get you onto DaGaHa_Build?

To join, enter client.connect 147.147.153.164:28015 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 mp50,ptrak,$r?,v2635,gmrust,cs167528,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs167528
Build Game build: 167528.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

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.