Offline 15.204.83.240:21000 checked 16d ago
typical TESTING
Connect
srv = rust.server("15.204.83.240:21001")
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 8 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 71% 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 1- map
- Procedural Map
- size
- 1000
- seed
- 1
Server
srv.info()- address
- 15.204.83.240:21000
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 07:25 UTC
- hostname
- –
- first seen
- 8 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 · 482 on average | 47/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 321 on average | 84/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 284 on average | 218/250 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 279 on average | 8/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 278/325 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 257 on average | 267/275 |
Quick answers
From the figures on this page.
Population data
How does typical TESTING compare in the rankings?
Rank #15,244 on seven-day player hours for typical TESTING, within the top 71% of all ranked servers.
How full does typical TESTING run?
Offline now for typical TESTING, with the last sample 16 days 5 hours ago.
Server data
What is the Rust version on typical TESTING?
Version Rust network protocol 2634 and build 167398 on Linux is reported by typical TESTING. The protocol has to match before you can join, and Steam does the updating.
Is typical TESTING up, and what does its uptime show?
typical TESTING is offline at this refresh; the last response came 16 days 5 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 8 October 2026.
Which location does typical TESTING run from?
For typical TESTING, 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:21000.
Map and rules
Which settings and rules does typical TESTING run?
You will not find a gather rate in the string typical TESTING. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.
Which map has typical TESTING selected?
typical TESTING runs a procedural map of size 1,000 with seed 1, 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 TESTING wipe?
A rhythm cannot be read from the wipes of typical TESTING on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 22 days 20 hours ago.
Tags and filters
Which lists on Rust Data hold typical TESTING, and which filters?
On Rust Data, typical TESTING appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on typical TESTING?
These tags are published by typical TESTING and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into typical TESTING?
Enter client.connect 15.204.83.240:21000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.