typical test
Online 104.153.151.75:28015 checked 11m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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
daily · 1 is bestTop 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
every wipe as a delivery, newest first- 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.
- ShockRust | Blue | NoLimit 30 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 127 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 43 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 33 / 700
- RustSpain.com | EU Main 9 / 200
- CSL Scenery Budget Test 0 / 500
Quick answers
From the figures on this page.
Player activity
How does typical test compare with other Rust servers in the rankings?
In the top 68% of all ranked servers sits typical test, at #15,075 on hours played over seven days.
Is typical test busy at the moment?
The current count is 0 players on 100 slots for typical test. Averaged over the past week: 0 players, peaking at 1. Over the last 48 hours, the peak hour came at 05:00 UTC with an average of 0 players.
Map and rules
Which map is active on typical test?
The game generates the procedural map on typical test at size 1,000 with seed 6738. You can see the map on RustMaps from this page, since one size and seed give one map.
What are the rules on typical test, and what settings does it run?
No gather rate appears in the name of typical test. Up to 8 players can join a group, the default for the game. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players is allowed. Plugins or settings alter the game on this one, which sits under Modded in the server browser. The plugins run on Oxide. VAC, the anti-cheat from Valve, is active.
Operator and location
What is the location of typical test?
There is no region published for typical test. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. The address to connect to is 104.153.151.75:28015.
What is the performance like on typical test?
The 48-hour average for server fps stands at 240, never dipping below 239. Buildings, deployables and all the rest of the world pushed its entity count as high as 3,864. 1,472 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.
Is typical test up, and how good is its uptime?
You can find typical test online at present. The uptime it reports puts its last restart at about 28 hours ago. It stayed up 100% of the time across the last 1 full day, which is 24 of 24 hours. 26 October 2026 is when Rust Wipe Tracker first recorded it.
On what Rust version does typical test operate?
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.
Map resets
How often does typical test wipe, and at what times?
There are too few of typical test's wipes on record so far to show its rhythm. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. You are playing a world created 2 days 1 hours.
Tags and filters
Where does typical test appear in Rust Wipe Tracker lists and filters?
You will find typical test on the following Rust Wipe Tracker lists: Modded Rust servers. You will find it under these 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.
How should you read the tags on typical test?
gmrust (Game mode): Standard Rust survival is the game mode here; mp100 (Max players): It holds 100 slots; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings, hence the Modded listing are the tags typical test publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.
Connecting
How do you connect to typical test?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 104.153.151.75:28015.