RUST METRICSFlight deck · live data
Data live Servers11,826 Players80,135 Populated3,731 Fresh wipes 3 h265 Scan5 min
‹ All servers176.115.139.80:28015
Offline Full Queue Fresh wipe Wipe due No query

DG|TEST|67

Offline 176.115.139.80:28015 checked 8d 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,093top 59%
Last wipe8d agono schedule published
Next wipe–no wipe 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, measured since 20 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

When does DG|TEST|67 wipe?

Its rhythm cannot be told from the wipes of DG|TEST|67 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 8 days 15 hours ago the current world was made.

Tags

How should you read the tags on DG|TEST|67?

Tags published by DG|TEST|67, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show DG|TEST|67?

On Rust Metrics, DG|TEST|67 sits in these lists: 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.

Occupancy

Where does DG|TEST|67 sit in the rankings?

Player hours over seven days put DG|TEST|67 at #13,093, in the top 59% of all ranked servers.

What player count does DG|TEST|67 carry?

Status for DG|TEST|67: offline. Last seen 8 days 15 hours ago.

Server

Where does DG|TEST|67 sit?

Reading: location. DG|TEST|67 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 176.115.139.80:28015.

What Rust version is DG|TEST|67 on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by DG|TEST|67. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is DG|TEST|67, and is it online now?

Check: connection. DG|TEST|67 is offline at this moment. Last contact was 8 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 20 October 2026, recorded by Rust Metrics.

Map and rules

How is DG|TEST|67 configured, and what rules are in force?

No gather rate appears in the name: DG|TEST|67. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is DG|TEST|67 on?

Size 3,500 and seed 12345: the game generates the procedural map on DG|TEST|67 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

What do you do to join DG|TEST|67?

Press F1 in Rust and enter client.connect 176.115.139.80:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.