Skip to the page
RUST ANALYTICS
LIVE29,880PLY11,513SRV
QUOTE 91.108.0.73:28015 Online checked 13m ago

test

Players · last
1/ 75
+024h
1% 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
1/ 75
1% full
Change · 24h
+0
no reading a day ago
7-day average
1
peak 1
Rank
#9,410
top 43%
Rank · 7d ago
–
not ranked a week ago
Last wipe
18d ago
no schedule published
Next wipe
–
no wipe seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
6
player hours, last seven days
Map
–
Procedural Map
First seen
19 Oct 2026
no hostname published

Players

AveragePeak
00.250.50.75122:0023:0000:0001:0002:0003:00

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
15k10k15k20k19 Oct20 Oct

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

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
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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rusty Moose |US Biweekly|NA · groups of 12+ · biweekly · 374 on average300/350−84−21.9%
2Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 356 on average148/200−66−31.0%
3Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 339 on average85/200−28−25.1%
4Rustoria.co - EU East LongEU · groups of 12+ · monthly · 309 on average106/200+11+11.1%
5Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 292 on average62/200−52−45.5%
6Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 234 on average75/100−22−22.5%

Quick answers

from the figures on this page

Rules & Settings

How is test configured in terms of rules and settings?

The name of test carries no gather rate. Groups can contain a maximum of 8 players, the default for the game. 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. The server has VAC, Valve's anti-cheat, switched on.

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 #9,410 on player hours, in the top 43% of all ranked servers.

What is the population on test?

1 of 75 slots on test are filled at the moment. The mean over the last seven days is 1 players, reaching 1 at its highest. At 23:00 UTC in the last 48 hours, it averaged 1 players, the busiest hour.

Wipe Frequency

On what cycle does test wipe?

No rhythm can be told for test yet: too few of its wipes are on record. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 18 days 8 hours ago the current world was created.

Server Details

Where can test be found?

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.108.0.73:28015.

test is on which Rust version?

The build is Rust network protocol 2634 and build 167781 on Linux, running on test. The protocol has to match for you to join, and Steam applies that update.

What is the uptime and reliability of test?

The server is live: test is online. The earliest Rust Analytics saw it was 19 October 2026.

Server Tags

How should you interpret the tags on test?

The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp75 (Max players): It holds 75 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167781 (Build): It runs build 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set, which test publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.

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.

Joining the Server

What steps do I take to join test?

Type client.connect 91.108.0.73:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp75
Max players It holds 75 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2634
Protocol To join, your game needs protocol 2634.
cs167781
Build It runs build 167781.
ptrak
Networking Runs on RakNet, Rust's default 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.