typical
Offline 9.195.144.165:21006 checked 22d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestTop 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| 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
the same kind of game, then region, group limit, rate and wipes- 275/325
- 344/425
- 877/1000
- 49/100
- 934/1000
- 776/800
Quick answers
from the figures on this pageReset cycle
When does typical wipe?
To tell the rhythm of typical, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 22 days 12 hours ago the current world was made.
Tags
Which tags does typical carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from typical. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does typical appear in Rust Metrics lists and filters?
On Rust Metrics, typical sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does typical sit in the rankings?
Ranking for typical: #15,955 on seven-day player hours, top 72% of all ranked servers.
What is the population on typical?
typical is not responding; status offline, last seen 22 days 6 hours ago.
Operator and location
Which location does typical run from?
No region tag on typical. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 9.195.144.165:21006.
What Rust version is typical on?
Version check: Rust network protocol 2634 and build 166652 on Linux, run by typical. Matching protocol is required to join. Let Steam update your game.
Is typical up, and how often does it stay up?
typical reports offline. The last reading came 22 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 7 October 2026.
Settings and map
How is typical configured, and what rules are in force?
Reading the name gives no gather rate for typical. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is typical on?
The game generates a procedural map for typical.
Join
How can you get onto typical?
Check: join. Open Rust, press F1, then enter client.connect 9.195.144.165:21006. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.