typical test2
9.244.16.170:28019 checked 25d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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
Quick answers
Server rules
What settings does typical test2 run?
There is no gather rate in the name typical test2. That is the game's default: groups of up to 8 players. It runs survival, the usual game of gathering, building and raiding. Other players can be fought and raided. You will find it under Community in the server browser. VAC, Valve's anti-cheat, is switched on.
What is the map on typical test2?
A procedural map, generated by the game, is what typical test2 runs.
Population
How full is typical test2?
At present, typical test2 is offline and its last appearance was 25 days 14 hours ago.
What position does typical test2 hold in the server rankings?
In the top – of ranked servers, typical test2 holds #15,398 for player hours over the last seven days.
Server tags
What do typical test2's tags indicate?
What the game's server browser gets from typical test2 is this tag list: gmrust (Game mode): Standard survival gameplay; mp100 (Max players): The server has 100 slots; ts8 (Group limit): Teams max out at 8—the default setting for Rust; v2633 (Protocol): You'll need protocol 2633 on your game to join; cs164530 (Build): It runs build 164530; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code is set. Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.
Where does typical test2 appear in Rust Zerg Life lists?
These Rust Zerg Life lists include typical test2: Rust community servers for clans. Under these filters it shows on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
About the server
What is the uptime and reliability of typical test2?
No sign of typical test2 at present: it was last seen 25 days 14 hours ago. Across the last 7 full days, 0 of 168 hours were online, which is 0%. Its first appearance in Rust Zerg Life records is 19 September 2026.
Which Rust build does typical test2 use?
On Linux, typical test2 runs Rust network protocol 2633 and build 164530. You can only join if your game uses the same protocol, and Steam takes care of updating it.
Where can you find typical test2?
From typical test2, no region is published. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. Connect to it at 9.244.16.170:28019.
Wipe cycle
What schedule does typical test2 follow for wipes?
So few of typical test2's wipes are recorded that its rhythm cannot be told yet. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it is due next. 25 days 15 hours ago is when its present world was created.
How to join
What steps do I take to join typical test2?
You can join by opening the console with F1 and typing client.connect 9.244.16.170:28019. Or hit Launch Rust on this page to open Rust through Steam and connect.
Server tags
Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp100
ts8
v2633
cs164530
ptrak
$r?
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.