RUST METRICSFlight deck · live data
Data live Servers11,872 Players96,217 Populated4,094 Fresh wipes 3 h158 Scan5 min
‹ All servers40.27.19.2:28015
Offline Full Queue Fresh wipe Wipe due No query

GamerDaddyLive

Offline 40.27.19.2:28015 checked 26d ago

COM 1 · connect

Server instruments

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

Players now

0% 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#16,639top 70%
Last wipe27d 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
15k10k15k20k20 Sep23 Sep30 Sep3 Oct5 Oct8 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
Wed 30 Sep, 17:15 UTC27d 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 GamerDaddyLive when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does GamerDaddyLive follow?

To tell the rhythm of GamerDaddyLive, 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. 27 days 1 hours ago the current world was made.

Tags

How should you read the tags on GamerDaddyLive?

Tags published by GamerDaddyLive, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166388 (Build): Game build reading: 166388; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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 GamerDaddyLive?

These Rust Metrics lists carry GamerDaddyLive: 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.

Occupancy

What position does GamerDaddyLive hold among Rust servers?

Player hours over seven days put GamerDaddyLive at #16,639, in the top 70% of all ranked servers.

How full does GamerDaddyLive get?

Status for GamerDaddyLive: offline. Last seen 26 days 14 hours ago.

Operator and location

Where does GamerDaddyLive sit?

No region comes from GamerDaddyLive. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 40.27.19.2:28015.

What Rust version is GamerDaddyLive on?

Rust network protocol 2634 and build 166388 on Windows is the build GamerDaddyLive runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is GamerDaddyLive, and is it online now?

GamerDaddyLive reports offline. The last reading came 26 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 14 September 2026, recorded by Rust Metrics.

Settings and map

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

Reading the name gives no gather rate for GamerDaddyLive. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is GamerDaddyLive on?

The game generates a procedural map for GamerDaddyLive.

How to join

How do you connect to GamerDaddyLive?

Check: join. Open Rust, press F1, then enter client.connect 40.27.19.2: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?,v2634,gmrust,cs166388,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166388
Build Game build reading: 166388.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.