Skip to the page
RUST ANALYTICS
LIVE31,206PLY11,454SRV
QUOTE 9.195.144.165:21000 Offline checked 7d ago

typical TESTING

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
#15,955
top 72%
Rank · 7d ago
#16,709
754 places up
Last wipe
7d 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
7 Oct 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
15k10k15k20k7 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

Top 72% 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
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 398 on average141/200−11−7.1%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 335 on average70/200−48−40.8%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 324 on average349/375+108+45.1%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 316 on average94/200+2+2.1%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average14/250+2+17.6%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 271 on average22/100−71−76.3%

Quick answers

from the figures on this page

Server Rules

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

The name of typical TESTING carries no gather rate. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. You can fight and raid other players. Community is its listing in the server browser. VAC is active.

Which map is played on typical TESTING?

typical TESTING uses a procedural map, which the game generates.

Player Count

Where does typical TESTING sit in the rankings?

For the last seven days, typical TESTING holds rank #15,955 on player hours, in the top 72% of all ranked servers.

How many players does typical TESTING have?

At present, typical TESTING is offline; the last sighting was 7 days 15 hours ago.

Wipe Schedule

When does typical TESTING schedule its wipes?

There are too few wipes on record for typical TESTING to reveal its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. 7 days 21 hours ago the current world was created.

Server Details

Where can typical TESTING be found?

No region is published by typical TESTING. Rust Analytics reports the location a server claims, not the machine's actual location. 9.195.144.165:21000 is its address.

typical TESTING is on which Rust version?

The version in use at typical TESTING: Rust network protocol 2634 and build 166652, on Linux. Joining requires the same protocol on your game, which Steam updates.

Is typical TESTING up, and how consistent is its uptime?

typical TESTING is down. The last time we saw it was 7 days 15 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. First sighting by Rust Analytics: 7 October 2026.

Tags & Filters

What is the meaning of the tags on typical TESTING?

These tags are published by typical TESTING and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp40 (Max players): Slot count: 40; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166652 (Build): It runs build 166652; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set. Also in the tags and at the top of this page: current players, queue and world creation time.

Where does typical TESTING show up in Rust Analytics lists and filters?

On Rust Analytics, typical TESTING 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 2 weeks.

Joining the Server

How can I connect to typical TESTING?

Type client.connect 9.195.144.165:21000 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 mp40,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival in the standard Rust format.
mp40
Max players Slot count: 40.
ts8
Group limit At the game default, teams hold up to 8.
v2634
Protocol Your game must run protocol 2634 to connect.
cs166652
Build It runs build 166652.
ptrak
Networking RakNet, the network layer the game ships with.
$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.