Statistical profileOnline
typical test
104.153.151.75:28015 checked 14m ago
Connect to this server
1. Main points
Players now
0/ 100
0% full
7-day average
0
peak 1
Rank
#15,059
top 68%
Last wipe
2d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- There were 0 players on it, 0% of its 100 slots.
- Over the last seven days it averaged 0 players, with a peak of 1.
- It ranks #15,059 of all ranked servers, the top 68%, on player hours over the last seven days.
- Its current map went up 2d ago.
2. Players
Figure 1: Players on typical test
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of typical test
1000 · seed 6738
8. Server characteristics
Table 3: Characteristics of typical test
What the server publishes and what was recorded
| Address | 104.153.151.75:28015 |
|---|---|
| Region | – |
| Max players | 100 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 26 Oct 2026, 00:35 UTC |
| Hostname | – |
| First seen | 26 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 155 on average | 150 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 123 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 181 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 91 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 5 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 40 / 1000 |
10. Quick answers
From the figures on this page.
Wipe schedule
This release records the wipe timetable for typical test: what is it?
With too few wipes of typical test on record, its rhythm remains unclear. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. 2 days 8 hours have passed since this world was made.
Server details
What does the record show for the uptime and current status of typical test?
This release records typical test as online. The uptime it reports puts the last restart at about 35 hours ago. The figures for the last full day, 1 in all, show it up 100% of the time, 24 of 24 hours. The first sighting of it by Rust Census was on 26 October 2026.
What does the performance record of typical test show?
The figures for the last 48 hours give an average of 240 server fps and a minimum of 239. Buildings, deployables and everything else in the world took the entity count to 3,864. The peak memory use recorded was 1,564 MB. What players experience as lag is low fps combined with a climbing entity count.
What location has been recorded for typical test?
A region is not published by typical test. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. 104.153.151.75:28015 is its address.
What version of Rust has been recorded on typical test?
Rust network protocol 2635 and build 168909 on Linux is the version typical test runs. To join, your game has to be on the same protocol; Steam handles the update.
Population
What population has been recorded on typical test?
At counting time typical test recorded 0 players across 100 slots. This release records a seven-day average of 0 players and a peak of 1.
What position does typical test hold in the server rankings?
The rank for typical test is #15,059 on seven-day player hours, in the top 68% of ranked servers.
Tag details
Where does typical test appear among the Rust Census lists and filters?
These Rust Census lists include typical test: Modded Rust servers, counted. It appears 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.
The tags on typical test: what do they indicate?
gmrust (Game mode): Survival play, in the standard Rust format; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): This server is listed as modded, with plugins or settings that change the game are the tags typical test publishes, and the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
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. Because one size and seed give one map, RustMaps can display it from this page.
How is typical test configured, and what rules does it keep?
The name of typical test carries no gather rate. The group cap stands at 8 players, the default for the game. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Plugins or settings change the game, and the browser lists it under Modded. Plugins on it number Oxide. Anti-cheat is active: VAC, Valve's system, is on.
Connecting
What is the way to join typical test?
Enter client.connect 104.153.151.75:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp100 | Max players 100 slots are available. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2635 | Protocol To connect, your game version must match protocol 2635. |
cs168909 | Build Game build: 168909. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded This server is listed as modded, with plugins or settings that change the game. |
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.