Skip to the page
RUST ANALYTICS
LIVE40,859PLY11,465SRV
QUOTE 91.200.52.59:28015 Offline checked 11h ago

TEST

Players · last
0/ 10
−1−100.0%24h
0% full
Day range 0 1
7-day avg 1 peak 1
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 10
0% full
Change · 24h
−1
−100.0% from 1
7-day average
1
peak 1
Rank
#8,987
top 40%
Rank · 7d ago
–
not ranked a week ago
Last wipe
1d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
8
player hours, last seven days
Map
–
Procedural Map
First seen
20 Sep 2026
no hostname published

Players

AveragePeakWipe
00.250.50.75114:0019:0021:0009:0018:0020:00Wiped Mon 12 Oct, 19:27 UTCWIPE

Hourly average and peak, UTC. Busiest hour of the two days: 1 players.

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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep22 Sep24 Sep26 Sep12 Oct14 Oct

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

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.

usual gap
3.1 days
between real wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 19:27 UTC1d ago – – running 1
Fri 9 Oct, 17:59 UTC4d ago – – 3.1 days 1

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 406 on average320/325−1−0.4%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 355 on average162/225−17−9.5%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 336 on average199/250+22+12.5%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 333 on average164/200−18−9.8%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 299 on average28/250−11−29.0%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 281 on average167/175−1−0.5%

Quick answers

from the figures on this page

Map and Rules

What settings and rules are in place on TEST?

No gather rate is given in the name of TEST. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. You will find it under Community in the server browser: it is a community server. VAC, Valve's anti-cheat, is enabled.

Which map is played on TEST?

A procedural map runs on TEST, created by the game.

Population

What is the rank of TEST?

For the last seven days, TEST holds rank #8,987 on player hours, in the top 40% of all ranked servers.

How many players does TEST have?

At present, TEST is offline; the last sighting was 11 hours ago. Average players over seven days: 1; peak: 1. At 15:00 UTC in the last 48 hours, it averaged 1 players, the busiest hour.

Wipe Frequency

How often does TEST wipe?

No rhythm can be told for TEST yet: too few of its wipes are on record. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. This world has been running for 37 hours.

Server Info

What is the server location for TEST?

For TEST, no region is published. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 91.200.52.59:28015.

TEST runs which version of Rust?

Rust network protocol 2634 and build 167398 on Windows is what TEST runs. The protocol has to match for you to join, and Steam applies that update.

What is the uptime and reliability of TEST?

No response from TEST. It was last seen 11 hours ago. 7 full days have passed with 7% uptime, 11 of 168 hours. The earliest Rust Analytics saw it was 20 September 2026.

Server Tags

How should you interpret the tags on TEST?

Published by TEST for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): It holds 10 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167398 (Build): Game build: 167398; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set. The top of this page and the tags both show its players now, its queue and when its world was made.

TEST appears in which of the lists and filters on Rust Analytics?

On Rust Analytics, TEST matches these lists: Rust community servers. 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 3 days.

Connection

How can I connect to TEST?

The console route: start Rust, press F1, enter client.connect 91.200.52.59:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.

Server tags

what each one means

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

Game

gmrust
Game mode Rust's standard survival mode.
mp10
Max players It holds 10 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2634
Protocol Your game must run protocol 2634 to connect.
cs167398
Build Game build: 167398.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code No region code has been 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.