typical test
Key statistics
the figures behind the quote- Players now
- 0/ 100 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,894 top 72%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 3d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- 1000 Procedural Map · seed 6738
- First seen
- 11 Oct 2026 no hostname published
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, measured since 11 Oct. 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
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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 129 on average | 52/300 | ▼−20−27.8% | |
| 2 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 91/100 | ▪+0+0.5% | |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 86 on average | 7/1000 | ▼−17−70.4% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 74 on average | 1/1000 | ▼−5−82.6% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 71 on average | 15/700 | ▼−3−17.4% | |
| 6 | RustSpain.com | EU MainEU · groups of 12+ · weekly · 67 on average | 4/200 | ▪+0+7.3% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on typical test?
No gather rate appears in the name of typical test. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. VAC is active.
What is the current map on typical test?
typical test uses a procedural map of size 1,000 with seed 6738, generated by the game. You can see the map on RustMaps from this page, as the same size and seed give the same map.
Player Count
What is the rank of typical test?
For the last seven days, typical test holds rank #15,894 on player hours, in the top 72% of all ranked servers.
What is the population on typical test?
At present, typical test is offline; the last sighting was 32 hours ago. Average players over the last seven days: 0.
Wipe Frequency
When does typical test schedule its wipes?
There are too few wipes on record for typical test to reveal its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. 3 days 11 hours ago the current world was created.
Server Details
What is the location of typical test?
No region is published by typical test. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 15.204.83.240:20999 is its address.
Is typical test performing well?
Server fps over the last 48 hours: 240 on average, 240 at the lowest. At its peak it held 3,771 entities: buildings, deployables and the rest of the world. Up to 736 MB of memory was used. A climbing entity count plus low fps is the lag players report.
What Rust version is typical test running?
The version in use at typical test: Rust network protocol 2634 and build 167398, on Linux. The protocol has to match for you to join, and Steam applies that update.
Is typical test up, and how consistent is its uptime?
No response from typical test. It was last seen 32 hours ago. Its own uptime figure dates the last restart to roughly 2 days 1 hours ago. The last 3 full days give 62% uptime, 45 hours on out of 72. The earliest Rust Analytics saw it was 11 October 2026.
Server Tags
How should you interpret the tags on typical test?
These tags are published by typical test and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): Slot count: 100; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167398 (Build): Build 167398; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Modded listing: the game is changed by plugins or settings. Also in the tags and at the top of this page: current players, queue and world creation time.
On Rust Analytics, which lists and filters feature typical test?
These Rust Analytics lists include typical test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Joining the Server
What is the process to join typical test?
Type client.connect 15.204.83.240:20999 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
mp100
ts8
v2634
cs167398
ptrak
$r?
Mods and access
^o
^z
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.