Test
Offline 83.142.15.36:28015 checked 37d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
every wipe as a delivery, newest first- 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- Rusty Moose |EU Mondays| 784 / 825
- Rustoria.co - EU Main 50 / 250
- Rusty Moose |EU Main| 125 / 250
- Rustoria.co - EU East Long 463 / 500
- Rustoria.co - EU East Medium 268 / 300
- Rustafied.com - EU Friday 196 / 300
Quick answers
From the figures on this page.
Population
What is the ranking of Test against other Rust servers?
Over the past seven days, Test has climbed to #13,979 for player hours, putting it in the top – of all ranked servers.
How many players are on Test right now?
At the moment Test is offline, having last been seen 37 days 23 hours ago.
Server rules
On what map does Test take place?
A procedural map, generated by the game, is what Test runs.
What settings and rules should you know for Test?
No gather rate appears in the name of Test. 8 players is the group limit, since the game's default applies. You get survival here, the usual game: build, gather, raid. Fighting and raiding between players is allowed. The server browser files it under Community, as a community server. The VAC anti-cheat from Valve is enabled.
About the server
What is the location of Test?
No region is published by Test. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. 83.142.15.36:28015 is its address.
Is Test up, and how good is its uptime?
Offline for now: Test was last seen 37 days 23 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. 19 September 2026 is when Rust Wipe Tracker first recorded it.
On what Rust version does Test operate?
On Windows, Test runs Rust network protocol 2633 and build 164530. To join, your game must be on the same protocol; Steam handles that update for you.
Wipe schedule
When does Test wipe? What schedule does it follow?
Its rhythm cannot yet be told: too few of Test's wipes are on record. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 52 days 4 hours.
Tags and listings
Where does Test appear across the Rust Wipe Tracker lists and filters?
These Rust Wipe Tracker lists take Test: Rust community servers, unmodded. On the server list, apply Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it appears.
What is the meaning of the server tags on Test?
gmrust (Game mode): Standard Rust survival is the game mode here; mp3 (Max players): It holds 3 slots; ts8 (Group limit): Team limit: 8, the standard default; v2633 (Protocol): Protocol 2633 is required; a different version can't join; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set are the tags Test publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.
How to join
How do you connect to Test?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 83.142.15.36:28015.