Offline 122.37.142.29:28015 checked 1d ago
Testing on param
Connect
srv = rust.server("122.37.142.29: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. 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 69% 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 122.37.142.29:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 06:50 UTC
- hostname
- –
- first seen
- 27 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 · 151 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 96/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 31/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 10/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Testing on param take in the server rankings?
Player hours over seven days put Testing on param at #15,341, in the top 69% of the ranked set.
How full does Testing on param run?
Offline now for Testing on param, with the last sample 47 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does Testing on param run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Testing on param. The protocol has to match before you can join, and Steam does the updating.
Is Testing on param up, and what does its uptime show?
The latest sample has Testing on param offline, with a last sighting 47 hours ago. Over the last 1 full day the hours up number 0 of 24, 0%. The first row Rust Data holds for it is dated 27 October 2026.
Which location does Testing on param run from?
For Testing on param, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 122.37.142.29:28015 is its address.
Rules, settings, map
Which settings and rules does Testing on param run?
No gather rate appears in the name: Testing on param. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Testing on param loaded?
A procedural map runs on Testing on param, generated by the game.
Wipes and dates
When does Testing on param wipe, and on what schedule?
Too few wipes are on record for Testing on param 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 47 hours ago.
Tags, lists
Which lists on Rust Data hold Testing on param, and which filters?
These Rust Data lists include Testing on param: 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 Testing on param hold?
The game's server browser reads these tags from Testing on param: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 Testing on param?
Enter client.connect 122.37.142.29:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.