typical
Offline 15.204.83.240:21006 checked 15d 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 71% 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- 366/425
- 457/500
- 980/1000
- 53/100
- 964/1000
- 32/250
Quick answers
from the figures on this pageReset cycle
How often does typical wipe, and when?
To tell the rhythm of typical, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 22 days 9 hours ago.
Lists and filters
How should you read the tags on typical?
Tags published by typical, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): Slots: 40; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Game build reading: 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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?
These Rust Metrics lists carry typical: Rust community servers: live readings. 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.
Player count
What position does typical hold among Rust servers?
Player hours over seven days put typical at #15,244, in the top 71% of all ranked servers.
What player count does typical carry?
typical is not responding; status offline, last seen 15 days 18 hours ago.
Server details
What location is typical hosted in?
No region comes from typical. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 15.204.83.240:21006.
What Rust version is typical on?
Reading: typical, Rust network protocol 2634 and build 167398, Linux. Matching protocol is required to join. Let Steam update your game.
What is the uptime on typical, and is it online?
Check: connection. typical is offline at this moment. Last contact was 15 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 8 October 2026, recorded by Rust Metrics.
Map and rules
What rules does typical enforce, and what are its settings?
Reading the name gives no gather rate for typical. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
What map is typical on?
The game generates a procedural map for typical.
How to join
How do you connect to typical?
Check: join. Open Rust, press F1, then enter client.connect 15.204.83.240:21006. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.