Local forecast
Testing on param
Offline 122.37.142.29:28015 checked 1d ago
Current conditions
observed 1d agoplayers now
0% full
- 7-day average
- 0
- peak –
- Rank
- #15,348
- top 69%
- Last wipe
- 1d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
Next wipe
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer facts
Is Testing on param online at the moment, and how consistent is its uptime?
Testing on param is currently offline, with the last sighting 38 hours ago. The first sighting by Rust Wipe Stats was on 27 October 2026.
Where does Testing on param run from?
No region is published by Testing on param. Where a server says it is, that is what Rust Wipe Stats shows; it does not look up the machine's actual location. You can reach it at 122.37.142.29:28015.
What Rust version is Testing on param on?
On Testing on param you will find Rust network protocol 2635 and build 168909, hosted on Windows. The protocol must match for you to join, and Steam keeps it updated.
Tags, lists and filters
Which meaning sits behind each tag on Testing on param?
The server browser reads these tags from Testing on param: gmrust (Game mode): The mode is plain Rust survival; mp500 (Max players): It holds 500 players; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Joining needs game protocol 2635 on your copy of the game; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the network layer, as standard for the game; $r? (Region code): This server carries no region code; ^o (Oxide): It runs on Oxide, also called uMod, for plugins; ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.
Where does Testing on param appear among the Rust Wipe Stats lists and filters?
The Rust Wipe Stats lists that include Testing on param are: Modded Rust servers. These filters on the server list will bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
Which map is in use on Testing on param?
The map is procedural, generated by the game on Testing on param.
What settings does Testing on param use, and what rules does it enforce?
The name of Testing on param says nothing about gather rate. The default of 8 players is the group limit here. It plays as survival, gathering, building and raiding, as the game normally plays. Raiding and player combat are both allowed. Plugins or settings change the game here, and the browser files it under Modded. Oxide are the plugin frameworks it runs. Valve anti-cheat (VAC) runs on this server.
Wipe schedule
Which days and times does Testing on param schedule its wipes for?
Its rhythm cannot be read yet, as too few of Testing on param's wipes are on record. A monthly force wipe hits every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The current map and world began 38 hours.
Population
How many players does Testing on param hold?
At this moment Testing on param is down, having last been seen 38 hours ago. The seven-day average stands at 0 players.
How does Testing on param compare with other Rust servers in the rankings?
Player hours over the past week put Testing on param at #15,348, inside the top 69% of all ranked servers.
How to join
What steps let you join Testing on param?
Two ways in: press F1 and enter client.connect 122.37.142.29:28015, or join from this page with Launch Rust, which opens Steam and connects you.