Online 104.153.151.75:28015 checked 12m ago
typical test
Connect
srv = rust.server("104.153.151.75:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
1000 · seed 6738
- map
- Procedural Map
- size
- 1000
- seed
- 6738
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 161 on average | 32/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 41/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 28/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 9/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 8/1000 |
Quick answers
From the figures on this page.
Population
What position does typical test take in the server rankings?
Over the last seven days typical test sits at #15,074 on player hours, in the top 68% of ranked servers.
How full does typical test run?
Current row: 0 players on typical test, against 100 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 05:00 UTC, mean 0 players.
About the server
What does performance look like on typical test?
Server fps over the last 48 hours averages 240; the floor is 239. Buildings, deployables and all else in the world took the count as high as 3,864 entities. Memory peaked at 1,472 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is typical test on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by typical test. Steam updates your game for you, but the protocol must match to join.
How reliable is typical test, and is it up?
The current sample puts typical test online. The uptime it reports puts the last restart about 28 hours ago. Over the last 1 full day the hours up number 24 of 24, 100%. Rust Data logged it first on 26 October 2026.
In which location is typical test hosted?
There is no region published for typical test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 104.153.151.75:28015 is its address.
Rules, settings, map
What rules and settings are recorded for typical test?
You will not find a gather rate in the string typical test. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
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; this page links to RustMaps so it can be viewed.
Wipe schedule
When does typical test wipe, and on what schedule?
Too few wipes are on record for typical test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 2 days 1 hours ago.
Lists and tags
Which Rust Data filters and lists contain typical test?
These Rust Data lists include typical test: 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 3 days.
Which meanings do the tags on typical test hold?
The game's server browser reads these tags from typical test: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join typical test?
The manual route: launch Rust, F1, then client.connect 104.153.151.75:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.