Server profile
typical test
Online, with 0 of 100 players on; ranked #15,070 of every public Rust server, the top 68%. It last wiped 1d ago.
Online 104.153.151.75:28015 checked 11m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 68% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe days
On what schedule does typical test wipe?
The record of typical test's wipes is too thin yet to show its rhythm. The monthly force wipe comes to all Rust servers next on Thursday 5 November at 19:00 UTC. 47 hours have passed since its current world was created.
Server details
Does typical test hold a steady frame rate?
Server fps averaged 240 over 48 hours; the lowest reading was 239. At its highest the entity count reached 3,864: buildings, deployables and everything else. The highest memory figure was 1,472 MB. A climbing entity count and low fps are what players experience as lag.
On what version does typical test currently run?
Rust network protocol 2635 and build 168909 on Linux is what typical test runs. The same protocol is required to join, and Steam takes care of updating it.
What does uptime look like for typical test, and is it online?
typical test is currently reachable and online. About 26 hours ago is when it last restarted, judged from the uptime it reports. Of the 24 hours in the last 1 full day, 0 were up, 0% of the time. Rust Insights first logged this server on 26 October 2026.
What location is listed for typical test?
There is no region published for typical test. The location shown on Rust Insights is the one a server states, not a lookup of where the machine sits. You can reach it at 104.153.151.75:28015.
Server tags
What is meant by each tag on typical test?
When the game's server browser reads typical test, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): Your game must run the same version to join: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Modded is its listing, because plugins or settings change how the game plays. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
Where does typical test turn up among the Rust Insights lists and filters?
typical test appears among the following Rust Insights lists: Modded Rust servers, explained. You will find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Player counts
How many players are on typical test right now, and how does that number move?
typical test shows 0 players at the moment, against 100 slots. A weekly average of 0 players goes with a peak of 1. Look at the last 48 hours and the peak hour is 05:00 UTC, at 0 players on average.
In the ranking of Rust servers, where does typical test place?
The player-hours ranking for the last seven days puts typical test at #15,070, among the top 68% of all ranked servers.
Settings and rules
What are the settings and rules for typical test?
Nothing about gather rate is given in the name of typical test. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. Players may raid and fight one another. Plugins or settings change the game, so it sits under Modded in the browser. Oxide is the plugin count it runs. VAC is on: Valve's anti-cheat is active.
What is the map on typical test?
The game generates the map on typical test: procedural, size 1,000, seed 6738. The same size and seed produce the same map, so from this page you can look at it on RustMaps.
Join
What is the way to join typical test?
Open the console with F1 in Rust and enter client.connect 104.153.151.75:28015. You can skip the console by using Launch Rust here, which starts Rust through Steam and connects you.