Element card · group Community · atomic number 15,398, its rank

typical tst 3

Offline 9.244.16.170:28021 checked 39d ago

Join the experiment

Launch Rust and join

Atomic mass · players now 0/ 100 0% full Room to join

7-day average0peak –

Rank · atomic number#15,398no region published

Last wipe39d agono schedule published

Next wipe–too few wipes seen yet

Result 01

Players

Method

Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.

Result

No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method

Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.

Result

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region

Reaction kinetics

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

Reaction log

Wipes

newest first

Wiped	Peak	Crowd	Lasted	Players before
Sat 19 Sep, 06:13 UTC39d ago	0	–	running	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

1 Ru Rusty Moose |E… 636
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 550 on average 636/ 675
2 Ru Rustoria.co - … 485
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average 485/ 525
3 Ru Rusty Moose |E… 59
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 300 on average 59/ 250
4 Ru Rustoria.co - … 36
Rustoria.co - EU Main EU · groups of 16+ · weekly · 300 on average 36/ 250
5 Ru Rustafied.com … 138
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 269 on average 138/ 200
6 Ru Rustoria.co - … 255
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 257 on average 255/ 300

Quick answers

from the figures on this page

Map and rules

What map is in play on typical tst 3?

The map on typical tst 3 is procedural, made by the game.

What settings and rules apply on typical tst 3?

Nothing in the name of typical tst 3 gives a gather rate. Eight players per group is the limit, the game's default. survival is the game mode, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. You will find it under Community in the server browser. VAC is on, Valve's anti-cheat.

About the server

In what location does typical tst 3 sit?

Nothing about a region is published by typical tst 3. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. Connect at 9.244.16.170:28021.

What Rust version does typical tst 3 currently run?

Rust network protocol 2633 and build 164530 on Linux is what typical tst 3 uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is typical tst 3 for staying online?

Currently offline, typical tst 3 was last seen 39 days 12 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. The first sighting by Rust Data Lab was on 18 September 2026.

Wipes and resets

When does typical tst 3 wipe, and how often?

typical tst 3's wipe history on record is too thin yet to tell its rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 39 days 12 hours ago the current world was made.

On typical tst 3, what happens when wipe day arrives?

At their busiest, recent wipes averaged 0 players. The latest wipe's peak fell 0 hours after it began.

Lists and tags

How should you read the tags on typical tst 3?

These are the tags typical tst 3 makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Player slots: 100; ts8 (Group limit): This uses the game's default: 8 per team; v2633 (Protocol): The server runs protocol 2633, so your game needs the same version; cs164530 (Build): The game build is 164530; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): A region code has not been set here. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Which Rust Data Lab filters and lists does typical tst 3 appear in?

The Rust Data Lab lists that include typical tst 3 are: Rust community servers, measured. Applying these filters on the server list returns it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Against other Rust servers, where does typical tst 3 place?

typical tst 3 sits at #15,398 for seven-day player hours, placing it in the top – of ranked servers.

What does the current player count on typical tst 3 tell you?

No live signal from typical tst 3 right now, which was last seen 39 days 12 hours ago.

Getting on

How can you connect to typical tst 3?

In Rust, press F1 and enter client.connect 9.244.16.170:28021. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8

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.