typical test
Online 104.153.151.75:28015 checked 13m 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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 68% 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
| 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.
Quick answers
From the figures on this page.
Map and rules
Where can you read the rules and settings that apply on typical test?
You will find no gather rate in the name of typical test. 8 players per group is the default limit. Filed under survival, gather, build and raid: the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. The server has VAC, Valve's anti-cheat, turned on.
Which map is in use on typical test?
typical test runs a procedural map of size 1,000 with seed 6738, generated by the game. You can view the map on RustMaps from this page, as the same size and seed give the same map.
Tags
Where does typical test appear among the Rust Server Index lists and filters?
The Rust Server Index lists that include typical test are Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
What is meant by the tags on typical test?
The server's own tags are listed here, and the game's server browser reads them: typical test gives gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): The queue ceiling sits at 100; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): Joining needs you on game protocol 2635; cs168909 (Build): The game build here is 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Modded: the game is changed by plugins or settings. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe schedule
How often is typical test wiped, and on what schedule?
Its rhythm is not yet clear, since the record holds too few of typical test's wipes. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. Its present world dates from 2 days 11 hours.
Population
Where does typical test sit in the rankings?
On player hours over seven days, typical test takes #15,084, within the top 68% of ranked servers.
Is typical test quiet or crowded?
Filed under live counts: typical test, 0 players on 100 slots at present. Filed under seven-day figures: an average of 0 players and a peak of 1.
Server facts
Which Rust build is typical test running?
Rust network protocol 2635 and build 168909 on Linux is what you will find on typical test. The protocol must match before you can join, and Steam takes care of updating it.
How reliable is typical test, and is it online now?
Right now typical test is up and running. Its reported uptime gives the last restart as roughly 38 hours ago. It was up 24 of 24 hours in the last 1 full day, or 100% of the time. It was first recorded by Rust Server Index on 26 October 2026.
How well does typical test perform?
The last 48 hours give an average of 240 server fps and a floor of 239. The entity count reached 3,864, covering buildings, deployables and all else in the world. Up to 1,654 MB of memory was in use. A climbing entity count and low fps are felt by players as lag.
Which region is typical test in?
There is no region on record for typical test; it publishes none. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 104.153.151.75:28015.
Connecting
What is the way onto typical test?
Enter client.connect 104.153.151.75:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp100
ts8
v2635
cs168909
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.