Rust Server Analytics 99,467 players11,887 servers
All servers
Drill-through Server detail

Testserver

Online 168.100.162.11:28075 checked 12m ago

Drill-through
FilterServeris Testserver
Attributes
vanillapremium
Last refreshed
Players now 0/ ?
7-day average 0 peak –
Rank #15,327 top 69%
Last wipe 17d ago no schedule published
Next wipe – no rhythm it keeps

Players

average and peak, with its wipes marked
AveragePeak
0123418:0003:0012:0021:0006:0015:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
01020304018:0003:0012:0021:0006:0015:00

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, measured since 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Sep29 Sep7 Oct14 Oct22 Oct29 Oct

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

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Sun 11 OctThu 1 OctMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 22:00 UTC17d ago 0 – running 0
Thu 1 Oct, 16:53 UTC28d ago 1+1 queue halved by day 1 10.2 days 0
Mon 28 Sep, 16:02 UTC31d ago 1 halved by day 1 3 days 0
Sat 26 Sep, 00:41 UTC33d ago 1 halved by day 1 2.6 days 0

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
ServerProfilePlayers now
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 514 on average 366 / 425
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average 459 / 500
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 280 on average 981 / 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 276 on average 59 / 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 265 on average 989 / 1000
Rustoria.co - US Main NA · groups of 16+ · weekly · 235 on average 27 / 250

Quick answers

from the figures on this page

Wipe data

The wipe schedule for Testserver: what is it?

With irregular wipe times, Testserver offers no next wipe to predict. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The world now in play was created 17 days 19 hours ago.

On Testserver, what happens on wipe day?

The average busiest count over recent wipes is 1 players. Peak population for the latest wipe came 0 hours after it began. Above half that peak until the next wipe held in 0% of recent wipes. The fall below half arrived by day 1 when it didn't hold.

Server details

What is the hosting location of Testserver?

A region is not published by Testserver. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 168.100.162.11:28075.

What Rust build does Testserver run?

On Linux, Testserver runs Rust network protocol 2635 and build 169606. The protocol has to match before you can join; Steam updates it automatically.

Is Testserver up, and how steady is its uptime?

As of the latest refresh, Testserver is online. About 12 hours ago is when it last restarted, judged by its reported uptime. Of 168 hours in the last 7 full days, 167 were up: 99%. It entered Rust Server Analytics records on 22 September 2026.

Does Testserver perform well?

Server fps averaged 30 over the last 48 hours, with a floor of 27. Buildings, deployables and all other world objects brought the entity total to 94,000. At its highest, memory use was 4,019 MB. Lag, for players, means low fps alongside a growing entity count.

Tags

Which meanings do the tags on Testserver carry?

The game's server browser reads the tags Testserver publishes: gmrust (Game mode): Survival in the standard Rust format; mp0 (Max players): Player slots: 0; ts16 (Group limit): The cap is 16 players per team; v2635 (Protocol): Joining needs your game on protocol 2635; cs169606 (Build): Build number 169606; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^v (Vanilla): Nothing altered from Facepunch's release: rates, kits and rules are stock; ^t (Tutorial on): The Facepunch tutorial can be used here by new players; ^q (Premium): Rust premium status is required to join; rustmaps (Custom tag): A custom tag, set by the owner or a plugin, outside the standard set. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does Testserver appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count Testserver among their servers: Rust tutorial servers, Community Rust servers, live and Vanilla Rust servers. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: Premium; Server tag: Vanilla ^v, Tutorial on ^t and Premium ^q; Group limit: 5 or more.

Player numbers

Against other Rust servers, how does Testserver compare?

Player hours for the last seven days place Testserver at #15,327, in the top 69% of the ranked field.

How many players does Testserver carry?

Testserver currently records 0 players. Averaged across seven days, the population is 0 players.

Settings

What settings and rules does Testserver use?

The name of Testserver does not state a gather rate. Players per group: up to 16. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser, it appears under Community. Its self-description is vanilla: nothing altered from Facepunch's release: rates, kits and rules are stock. Rust premium status is required to join. VAC, Valve's anti-cheat, is enabled.

The map on Testserver: which one is it?

Download the published map file for the custom map on Testserver, size 3,750, from this page.

How to join

What is the way onto Testserver?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 168.100.162.11:28075. Rust premium status is required to join. Find it online at https://www.rustafied.com/.

Server tags

what each one means

Published as mp0,ptrak,$r?,v2635,^v,^t,gmrust,cs169606,^q,ts16,rustmaps

Game

gmrust
Game mode Survival in the standard Rust format.
mp0
Max players Player slots: 0.
ts16
Group limit The cap is 16 players per team.
v2635
Protocol Joining needs your game on protocol 2635.
cs169606
Build Build number 169606.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been set.

Difficulty

^v
Vanilla Nothing altered from Facepunch's release: rates, kits and rules are stock.

Gameplay

^t
Tutorial on The Facepunch tutorial can be used here by new players.

Mods and access

^q
Premium Rust premium status is required to join.

Other

rustmaps
Custom tag A custom tag, set by the owner or a plugin, outside the standard 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.