Skip to the page
RUST ANALYTICS
LIVE82,048PLY11,709SRV
QUOTE 9.244.16.75:25565 Offline checked 2d ago

typical TEST

Players · last
0/ 40
n/a24h
0% full
Players · 24 hourshourly average, then now · dashed: 24 hours ago
No hourly readings in the last 24 hours.
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 40
0% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#16,161
top 70%
Rank · 7d ago
–
not ranked a week ago
Last wipe
2d ago
no schedule published
Next wipe
–
no wipe seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
0
player hours, last seven days
Map
–
Procedural Map
First seen
9 Nov 2026
no hostname published

Players

No hourly history yet.

Hourly average and peak, UTC.

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
15k10k15k20k10 Nov11 Nov

Top 70% 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 |EU Monthly|EU · groups of 12+ · monthly · 576 on average629/650−159−20.2%
2Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 565 on average60/250−223−78.8%
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 525 on average584/600−8−1.4%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 458 on average460/475−69−13.0%
5Magic Rust — Long | Kлaccикa x1 | PyccкийEU · groups of 150+ · 1x · monthly · 447 on average444/480−16−3.5%
6Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 400 on average463/550−115−20.0%

Quick answers

from the figures on this page

Server Rules

How is typical TEST configured in terms of rules and settings?

No gather rate is given in the name of typical TEST. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. The server browser lists it under Community, as a community server. VAC is active.

Which map is played on typical TEST?

The game generates the procedural map on typical TEST.

Activity

Where does typical TEST sit in the rankings?

For the last seven days, typical TEST holds rank #16,161 on player hours, in the top 70% of all ranked servers.

How many players does typical TEST have?

At present, typical TEST is offline; the last sighting was 2 days 15 hours ago. Average players over the last seven days: 0.

Wipe Cycle

How often does typical TEST wipe?

There are too few wipes on record for typical TEST to reveal its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 3 December at 19:00 UTC. This world has been running for 2 days 16 hours.

Server Info

Where can typical TEST be found?

No region is published by typical TEST. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 9.244.16.75:25565 is its address.

typical TEST runs which version of Rust?

The version in use at typical TEST: Rust network protocol 2636 and build 170545, on Linux. The protocol has to match for you to join, and Steam applies that update.

How reliable is typical TEST and is it currently online?

Offline at this moment: typical TEST. Last seen 2 days 15 hours ago. 2 full days have passed with 0% uptime, 0 of 48 hours. 9 November 2026 is when Rust Analytics first saw it.

Server Tags

How should you interpret the tags on typical TEST?

Published by typical TEST for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp40 (Max players): Slot count: 40; ts8 (Group limit): At the game default, teams hold up to 8; v2636 (Protocol): Your game must run protocol 2636 to connect; cs170545 (Build): Game build: 170545; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): Region code: none set. The top of this page and the tags both show its players now, its queue and when its world was made.

On Rust Analytics, which lists and filters feature typical TEST?

On Rust Analytics, typical TEST matches these lists: Rust community servers. 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; Last wipe: In the last 3 days.

Joining the Server

What steps do I take to join typical TEST?

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

Server tags

what each one means

Published as mp40,ptrak,$r?,v2636,gmrust,cs170545,ts8

Game

gmrust
Game mode Rust's standard survival mode.
mp40
Max players Slot count: 40.
ts8
Group limit At the game default, teams hold up to 8.
v2636
Protocol Your game must run protocol 2636 to connect.
cs170545
Build Game build: 170545.
ptrak
Networking RakNet, the network layer the game ships with.
$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.