RUST METRICSFlight deck · live data
Data live Servers11,880 Players96,217 Populated4,117 Fresh wipes 3 h156 Scan5 min
‹ All servers220.158.30.44:28015
Online Full Queue Fresh wipe Wipe due No query

gdpy

Online 220.158.30.44:28015 checked 12m ago

COM 1 · connect

Server instruments

last reading Tue 16:00 UTC
0 0.8 1.5 2.2 3 PAX 0 /3

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 149 SERVER FPS

Server fps

48 h low 127 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 48,036 ×1000

Entities

48 h range 46,059–48,393 · memory 2,168 MB
1239 ET SINCE RESTART 9D 21H

Uptime

9 days 21 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,369top 70%
Last wipe15d agono schedule published
Next wipe–too few wipes seen yet
Memory2,168MBat the last reading
REC 1

Players

AveragePeak
0123419:0004:0013:0022:0007:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040019:0004:0013:0022:0007:0016:00

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 17 Sep. 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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 70% 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 peak0players, 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 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 13:31 UTC15d ago 0 – 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.

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

What happens on gdpy when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

When does gdpy wipe?

To tell the rhythm of gdpy, too few of its wipes 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 it runs now was made 15 days 4 hours ago.

Tags

How should you read the tags on gdpy?

Tags published by gdpy, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp3 (Max players): 3 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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 gdpy?

Rust Metrics lists featuring gdpy: 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.

Occupancy

Where does gdpy sit in the rankings?

Ranking for gdpy: #15,369 on seven-day player hours, top 70% of all ranked servers.

What is the population on gdpy?

Current headcount on gdpy: 0 players, 3 slots available. Seven-day reading: 0 players on average.

Operator and location

Where does gdpy sit?

No region comes from gdpy. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 220.158.30.44:28015.

What Rust version is gdpy on?

Reading: gdpy, Rust network protocol 2634 and build 167781, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How does gdpy perform?

Check: fps. Average 193 server fps over the last 48 hours, low of 127. Within range. Peak entity count: 48,393. Buildings, deployables and all else included. Memory peak: 2,749 MB. What players call lag comes from low fps and an entity count on the rise.

Is gdpy up, and how often does it stay up?

Check: connection. gdpy is online at this moment. Reading: uptime. About 9 days 21 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What rules does gdpy enforce, and what are its settings?

Reading the name gives no gather rate for gdpy. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is gdpy on?

Check: map. Procedural, size 3,000, seed 50000, generated by the game on gdpy. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How can you get onto gdpy?

Press F1 in Rust and enter client.connect 220.158.30.44: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 mp3,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp3
Max players 3 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.