RUST METRICSFlight deck · live data
Data live Servers11,646 Players40,469 Populated2,963 Fresh wipes 3 h89 Scan5 min
‹ All servers78.232.32.9:28015
Offline Full Queue Fresh wipe Wipe due No query

Agava Home Server

Offline 78.232.32.9:28015 checked 13d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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,497top 62%
Last wipe13d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k14 Oct15 Oct17 Oct18 Oct20 Oct21 Oct

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

What wipe timing does Agava Home Server follow?

To tell the rhythm of Agava Home Server, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 13 days 14 hours ago.

Lists and filters

How should you read the tags on Agava Home Server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from Agava Home Server. 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 Agava Home Server?

Rust Metrics lists featuring Agava Home Server: 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.

Player count

Where does Agava Home Server sit in the rankings?

Player hours over seven days put Agava Home Server at #13,497, in the top 62% of all ranked servers.

What player count does Agava Home Server carry?

Reading for Agava Home Server: offline at this moment; last seen 13 days 3 hours ago.

Server details

What location is Agava Home Server hosted in?

No region tag on Agava Home Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 78.232.32.9:28015.

What Rust version is Agava Home Server on?

Reading: Agava Home Server, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Agava Home Server up, and how often does it stay up?

Agava Home Server reports offline. The last reading came 13 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 14 October 2026, recorded by Rust Metrics.

Rules and settings

How is Agava Home Server configured, and what rules are in force?

Reading the name gives no gather rate for Agava Home Server. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is Agava Home Server on?

Check: map. Procedural, generated by the game, on Agava Home Server.

Join

How can you get onto Agava Home Server?

To join: start Rust, press F1 and type client.connect 78.232.32.9:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.