Rust Data

rustdata.spaceservers89.217.32.218:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 89.217.32.218:28015 checked 1d ago

pgm3

Connect

srv = rust.server("89.217.32.218:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak –
rank #15,425 # top 69%
last wipe 17d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123420:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct

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

Wipe schedule

srv.wipe_schedule()

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
89.217.32.218:28015
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
10 Oct 2026, 23:02 UTC
hostname
–
first seen
26 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 532 on average220/250
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 327 on average15/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 325 on average21/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average126/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 278 on average38/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average40/100

Quick answers

From the figures on this page.

Player counts

How does pgm3 compare in the rankings?

Player hours over seven days put pgm3 at #15,425, in the top 69% of the ranked set.

How full does pgm3 run?

Offline now for pgm3, with the last sample 31 hours ago. Over the last seven days it averaged 0 players.

About the server

Which Rust version is pgm3 on?

The build is Rust network protocol 2635 and build 168909 on Windows, run by pgm3. The protocol has to match before you can join, and Steam does the updating.

Is pgm3 up, and what does its uptime show?

pgm3 is offline at this refresh; the last response came 31 hours ago. 0 of 24 hours up over the last 1 full day, or 0%. Rust Data logged it first on 26 October 2026.

Where does pgm3 sit?

There is no region published for pgm3. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 89.217.32.218:28015 is its address.

Map and rules

Which rules apply on pgm3, and what settings?

No gather rate appears in the name: pgm3. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

Which map has pgm3 selected?

The game generates its map: procedural, on pgm3.

Wipe data

On what schedule does pgm3 wipe?

A rhythm cannot be read from the wipes of pgm3 on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 17 days 5 hours ago.

Tags and filters

Which lists on Rust Data hold pgm3, and which filters?

The Rust Data lists that pgm3 fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on pgm3 hold?

The game's server browser reads these tags from pgm3: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to pgm3?

In Rust, F1 opens the console: type client.connect 89.217.32.218:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp500
Max players The server lists 500 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not 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.

Rust Data 34,587 players 11,597 servers online