typical test
Online 104.153.151.75:28015 checked 6m ago
Server instruments
last reading Tue 20:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 239 · below 20 is lag, below 10 is badEntities
48 h range 1,578–3,864 · memory 1,410 MBUptime
1 days 0 hours since its last restart, at the last readingPlayers
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
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
the same kind of game, then region, group limit, rate and wipes- 100/500
- 131/100
- 110/225
- 29/200
- 96/700
- 34/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does typical test follow?
The rhythm of typical test's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 45 hours ago.
Tag meanings
How should you read the tags on typical test?
Tags published by typical test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show typical test?
On Rust Metrics, typical test sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Occupancy
What position does typical test hold among Rust servers?
Ranking for typical test: #15,061 on seven-day player hours, top 68% of all ranked servers.
What is the population on typical test?
0 of 100 slots are filled on typical test right now. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 05:00 UTC, averaging 0 players at that hour.
Server
Which location does typical test run from?
No region tag on typical test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 104.153.151.75:28015.
What Rust version is typical test on?
Rust network protocol 2635 and build 168909 on Linux is the build typical test runs. To get in, your game needs the same protocol; Steam applies the update.
Is performance on typical test within range?
Reading: 240 server fps on average across the last 48 hours. It never dropped below 239. Check: entities. The peak was 3,864, counting buildings, deployables and the rest of the world. Memory peak: 1,410 MB. What players call lag comes from low fps and an entity count on the rise.
What is the uptime on typical test, and is it online?
typical test reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 24 hours ago. Reading: first seen 26 October 2026, recorded by Rust Metrics.
Map and rules
How is typical test configured, and what rules are in force?
No gather rate appears in the name: typical test. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
What map is typical test on?
Size 1,000 and seed 6738: the game generates the procedural map on typical test from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
What do you do to join typical test?
To join: start Rust, press F1 and type client.connect 104.153.151.75:28015. Or press Launch Rust here and Steam opens the game and connects you.