typical test
15.204.83.240:20999 checked 1d 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, 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
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 test run?
You will not find a gather rate in the name typical test. Up to 8 players can group, which is the game's default. It runs survival, the usual game of gathering, building and raiding. Other players can be fought and raided. This one sits under Modded in the browser: the game is changed by plugins or settings. It runs plugins: Oxide. VAC, Valve's anti-cheat, is switched on.
Which map is active on typical test?
Size 1,000, seed 6738, generated by the game: the procedural map on typical test. You can view it on RustMaps from this page, since the same size and seed give the same map.
Player count
What is the population like on typical test?
The server typical test is currently offline; it was last seen 30 hours ago. Its seven-day average stands at 0 players.
What is typical test's ranking?
For player hours over the last week, typical test is #15,900, which puts it in the top 72% of all ranked servers.
Tags and filters
How should you read the tags on typical test?
For the game's server browser, typical test publishes these tags: gmrust (Game mode): Survival in the standard Rust mode; mp100 (Max players): Capacity: 100; ts8 (Group limit): This uses the standard team limit of 8; v2634 (Protocol): You'll need protocol 2634 on your game to join; cs167398 (Build): The game build is 167398; ptrak (Networking): Standard RakNet networking is in use here; $r? (Region code): There's no region code here; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Modded category: the game is altered by plugins or settings. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.
Which Rust Zerg Life filters and lists cover typical test?
These Rust Zerg Life lists include typical test: Modded Rust servers for clans and zergs. Under these filters it shows on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
About the server
What is the uptime and reliability of typical test?
typical test is offline at the moment; the last time it was seen was 30 hours ago. The uptime figure it gives suggests it restarted around 2 days 1 hours ago. Across the last 3 full days, 45 of 72 hours were online, which is 62%. The first time Rust Zerg Life saw it was on 11 October 2026.
What is the performance like on typical test?
Over the past 48 hours, server fps averaged 240 and never dropped below 240. The world held as many as 3,771 entities, including buildings, deployables and everything else. The maximum memory it used was 736 MB. What players experience as lag comes from low fps and a rising entity count.
Which Rust build does typical test use?
Rust network protocol 2634 and build 167398 is what typical test runs, on Linux. The protocol must match for you to join, and Steam will update your game to that protocol.
What location does typical test use?
From typical test, no region is published. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. You can reach it at 15.204.83.240:20999.
Wipe cycle
What schedule does typical test follow for wipes?
With so few wipes on record for typical test, its pattern is not yet clear. Come Thursday 5 November at 19:00 UTC, the monthly force wipe arrives for every Rust server. The world in play right now was made 3 days 9 hours ago.
Connect
What steps do I take to join typical test?
Enter client.connect 15.204.83.240:20999 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you.
Server tags
Published 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.