RUST METRICSFlight deck · live data
Data live Servers11,866 Players94,541 Populated3,878 Fresh wipes 3 h396 Scan5 min
‹ All servers109.228.201.58:2633
Offline Full Queue Fresh wipe Wipe due No query

WindowsGSM - Server #2

Offline 109.228.201.58:2633 checked 40d 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,293no region published
Last wipe43d 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 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
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 peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 15 Sep, 19:48 UTC43d ago 1 – 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 should you expect from wipe day on WindowsGSM - Server #2?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

When does WindowsGSM - Server #2 wipe?

Its rhythm cannot be told from the wipes of WindowsGSM - Server #2 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 43 days 20 hours ago.

Tags

How should you read the tags on WindowsGSM - Server #2?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from WindowsGSM - Server #2. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show WindowsGSM - Server #2?

On Rust Metrics, WindowsGSM - Server #2 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.

Population

What position does WindowsGSM - Server #2 hold among Rust servers?

Ranking for WindowsGSM - Server #2: #13,293 on seven-day player hours, top – of all ranked servers.

What player count does WindowsGSM - Server #2 carry?

WindowsGSM - Server #2 is not responding; status offline, last seen 40 days 17 hours ago.

Operator and location

Where does WindowsGSM - Server #2 sit?

No region tag on WindowsGSM - Server #2. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 109.228.201.58:2633.

What Rust version is WindowsGSM - Server #2 on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by WindowsGSM - Server #2. Check: protocol. To join, your game must match; Steam handles the update.

Is WindowsGSM - Server #2 up, and how often does it stay up?

WindowsGSM - Server #2 reports offline. The last reading came 40 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What settings and rules apply on WindowsGSM - Server #2?

No gather rate appears in the name: WindowsGSM - Server #2. 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. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is WindowsGSM - Server #2 on?

The game generates a procedural map for WindowsGSM - Server #2.

How to join

How can you get onto WindowsGSM - Server #2?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.