A125/ 300 players
Modded#15,923
typical test
Offline 15.204.83.240:20999 checked 1d ago
moddedoxide
players now0of 100 slots
7-day average0peak –
rank#15,923top 72%
last wipe · restocked3d agono schedule published
next wipe · restock–no wipe seen yet
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 bestRankRank in region
Top 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A225/ 225 players
A388/ 100 players
B16/ 1000 players
B26/ 1000 players
B312/ 700 players
On the back of the pack
Quick answers
From the figures on this page.
Lists and tags
What is the meaning of the tags on typical test?
The server browser reads these tags that typical test publishes: gmrust (Game mode): The standard survival game mode; mp100 (Max players): The cap is 100; ts8 (Group limit): The default cap is 8 per team; v2634 (Protocol): Protocol 2634: your game must match to get in; cs167398 (Build): Game build: 167398; ptrak (Networking): Network runs on RakNet, the game's standard; $r? (Region code): The region code is left blank; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): It sits in Modded: plugins or settings make the difference. Player numbers, queue length and world age are tagged as well, and they sit at the top of this page.
On Rust Vending Machine, which lists and filters can you find typical test in?
The Rust Vending Machine lists that feature typical test are: 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.
Rules & map
Which map is currently on typical test?
A procedural map, size 1,000 with seed 6738, generated by the game, is what typical test runs. The map is the same for a given size and seed, so RustMaps can show it from this page.
What rules does typical test enforce, and what settings does it run?
The name of typical test gives no gather rate. 8 players is the default group size, and that is the cap here. survival is the game mode, the usual game of gathering, building and raiding. You can fight and raid other players. The server browser lists it as Modded: plugins or settings alter the game. You will find Oxide plugins running here. The server has VAC, Valve's anti-cheat, switched on.
Server details
What is the location of typical test?
No region is published by typical test. Rust Vending Machine displays the location a server gives and does not look up the machine's true place. You can reach it at 15.204.83.240:20999.
How reliable is typical test, and is it online now?
Right now typical test is not in stock, last seen 25 hours ago. Its uptime figure puts the last restart at roughly 2 days 1 hours ago. 45 of 72 hours online over the last 3 full days, or 62% uptime. The first sighting of it on Rust Vending Machine was 11 October 2026.
What is the performance like on typical test?
The 48-hour average for server fps is 240, and the floor was 229. The entity count reached 3,771: that includes buildings, deployables and everything else. At most it drew 736 MB of memory. The feel of lag traces back to fps dropping and entities piling up.
What Rust version does typical test run?
The setup: typical test on Linux, Rust network protocol 2634 and build 167398. To get in, your game must match the protocol; Steam keeps that updated.
Population
How does typical test compare to other Rust servers in the rankings?
Over the last seven days typical test ranks #15,923 on player hours, among the top 72% of all ranked servers.
Is typical test busy at the moment?
You will find typical test offline right now; its last sighting was 25 hours ago. Over the last seven days you would have seen 0 players on average.
Wipe info
On what schedule does typical test wipe?
Too few wipes of typical test are recorded to tell what its rhythm is. On Thursday 5 November at 19:00 UTC the monthly force wipe comes, and every Rust server wipes. The world it has now started 3 days 4 hours ago.
How to join
What is the way to join typical test?
Press F1 in Rust to bring up the console and enter client.connect 15.204.83.240:20999. Alternatively, the Launch Rust option on this page opens Rust via Steam and joins for you.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game mode The standard survival game mode.
mp100
Max players The cap is 100.
ts8
Group limit The default cap is 8 per team.
v2634
Protocol Protocol 2634: your game must match to get in.
cs167398
Build Game build: 167398.
ptrak
Networking Network runs on RakNet, the game's standard.
$r?
Region code The region code is left blank.
Mods and access
^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded It sits in Modded: plugins or settings make the difference.
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.