Skip to the page
RUST ANALYTICS
LIVE34,642PLY11,470SRV
QUOTE 60.56.65.96:28015 Offline checked 11d ago

TestServer

Players · last
1/ 1
n/a24h
100% 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
1/ 1
100% full
Change · 24h
n/a
no reading a day ago
7-day average
0
peak –
Rank
#13,818
top 60%
Rank · 7d ago
#7,451
6367 places down
Last wipe
12d ago
no schedule published
Next wipe
–
no wipe seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
1
player hours, last seven days
Map
–
Procedural Map
First seen
1 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
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 60% 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 · 408 on average164/200−2−1.4%
2Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 357 on average95/200−4−3.6%
3Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 339 on average348/400+57+19.5%
4Rustoria.co - EU LongEU · groups of 14+ · monthly · 335 on average97/200+6+6.0%
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 299 on average18/250−8−30.3%
6Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 282 on average90/125+17+24.1%

Quick answers

from the figures on this page

Map and Rules

What settings and rules are in place on TestServer?

No gather rate appears in the name of TestServer. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. You will find it under Community in the server browser: it is a community server. VAC, Valve's anti-cheat, is enabled.

What is the current map on TestServer?

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

Population

What position does TestServer hold in the server rankings?

For the last seven days, TestServer holds rank #13,818 on player hours, in the top 60% of all ranked servers.

How many players does TestServer have?

At present, TestServer is offline; the last sighting was 11 days 12 hours ago.

Wipe Schedule

How often does TestServer wipe?

There are too few wipes on record for TestServer to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. 12 days 6 hours ago the current world was created.

Server Overview

What is the location of TestServer?

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

TestServer is on which Rust version?

The version in use at TestServer: Rust network protocol 2634 and build 166494, on Windows. Joining requires the same protocol on your game, which Steam updates.

Is TestServer up, and how consistent is its uptime?

No response from TestServer. It was last seen 11 days 12 hours ago. The last 7 full days give 0% uptime, 0 hours on out of 168. 1 October 2026 is when Rust Analytics first saw it.

Server Tags

How should you interpret the tags on TestServer?

These tags are published by TestServer and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp1 (Max players): Slot count: 1; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166494 (Build): Build 166494; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): Region code: none set. The tags also carry its current players, queue and world creation time; this page shows them at the top.

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

The following Rust Analytics lists feature TestServer: 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 2 weeks.

Connection

What is the process to join TestServer?

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

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival in the standard Rust format.
mp1
Max players Slot count: 1.
ts8
Group limit Team size stays at the game default of 8.
v2634
Protocol Protocol 2634: matching game versions are required to join.
cs166494
Build Build 166494.
ptrak
Networking The standard network layer, RakNet.
$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.