RUST METRICSFlight deck · live data
Data live Servers11,803 Players69,659 Populated3,689 Fresh wipes 3 h126 Scan5 min
‹ All servers147.147.153.255:28015
Offline Full Queue Fresh wipe Wipe due No query

DaGaHa_Build

Offline 147.147.153.255:28015 checked 12d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% 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#13,419top 62%
Last wipe12d 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 Oct16 Oct18 Oct19 Oct21 Oct22 Oct

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

No hourly players around its wipes yet.

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, 17:01 UTC12d ago 1 – running 1

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

Reset cycle

What happens on DaGaHa_Build when wipe day comes?

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

What wipe timing does DaGaHa_Build follow?

The rhythm of DaGaHa_Build'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 in play was created 12 days 5 hours ago.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168160 (Build): Build 168160; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from DaGaHa_Build. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does DaGaHa_Build appear in Rust Metrics lists and filters?

Rust Metrics lists featuring DaGaHa_Build: Build and creative servers and Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

What position does DaGaHa_Build hold among Rust servers?

Ranking for DaGaHa_Build: #13,419 on seven-day player hours, top 62% of all ranked servers.

How full does DaGaHa_Build get?

Status for DaGaHa_Build: offline. Last seen 12 days 4 hours ago.

Server details

What location is DaGaHa_Build hosted in?

No region tag on DaGaHa_Build. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 147.147.153.255:28015.

What Rust version is DaGaHa_Build on?

Rust network protocol 2635 and build 168160 on Windows is the build DaGaHa_Build runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on DaGaHa_Build, and is it online?

Check: connection. DaGaHa_Build is offline at this moment. Last contact was 12 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 15 October 2026.

Map and rules

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

Check: gather rate. The name DaGaHa_Build does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is DaGaHa_Build on?

Check: map. Procedural, generated by the game, on DaGaHa_Build.

Connection

How do you connect to DaGaHa_Build?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168160,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168160
Build Build 168160.
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.