Offline 15.204.83.240:28015 checked 17d ago
typical testsss
Connect
srv = rust.server("15.204.83.240: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 4 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 best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 11 Oct, 03:08 UTC17d ago | 0 | NaN | running | 0 |
# 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
- 15.204.83.240:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 03:08 UTC
- hostname
- –
- first seen
- 4 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 560 on average | 237/275 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 157/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 292 on average | 27/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 291 on average | 14/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 31/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 43/200 |
Quick answers
From the figures on this page.
Population data
How does typical testsss compare in the rankings?
Player hours over seven days put typical testsss at #15,702, in the top 71% of the ranked set.
How many players does typical testsss hold at once?
The current row shows typical testsss offline; the last response was 17 days 4 hours ago.
About the server
Which Rust version is typical testsss on?
Rust network protocol 2634 and build 167398 on Linux is what typical testsss runs. Joining needs the same protocol on your game; Steam handles the update.
Is typical testsss up, and what does its uptime show?
The latest sample has typical testsss offline, with a last sighting 17 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 4 October 2026.
Where does typical testsss sit?
For typical testsss, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 15.204.83.240:28015.
Rules, settings, map
What rules and settings are recorded for typical testsss?
You will not find a gather rate in the string typical testsss. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Which map has typical testsss loaded?
typical testsss runs a procedural map of size 1,000 with seed 6738, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
On what schedule does typical testsss wipe?
Too few wipes are on record for typical testsss to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 17 days 21 hours ago, and that is the one in play.
What is wipe day on typical testsss like?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does typical testsss appear among Rust Data lists and filters?
On Rust Data, typical testsss appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on typical testsss hold?
The game's server browser reads these tags from typical testsss: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): The server runs build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into typical testsss?
The manual route: launch Rust, F1, then client.connect 15.204.83.240:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.