RS-15867Community server
typical TESTING
Offline 15.204.83.240:21000 checked 1d ago
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, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 72% 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.
Wipes
| 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Population
How populated is typical TESTING?
typical TESTING is offline at this moment; the last signal was 36 hours ago. The average over the last seven days comes to 0 players.
What is the ranking of typical TESTING?
On player hours across seven days, typical TESTING is #15,867, inside the top 72% of all ranked servers.
Tags, lists, and filters
Where does typical TESTING show up in Top Rust Servers lists and filters?
These Top Rust Servers lists count typical TESTING among their servers: Best Rust community servers. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on typical TESTING?
The game's server browser reads the tags that typical TESTING publishes: gmrust (Game mode): Survival follows the standard Rust ruleset; mp40 (Max players): It has 40 slots; ts8 (Group limit): The team limit is 8, which is the game default; v2634 (Protocol): Protocol 2634 is required to join; your game must be on the same version; cs167398 (Build): Game build: 167398; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): The region code is left blank. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Rules, settings, and map
What is the map on typical TESTING?
A procedural map of size 1,000 with seed 1, created by the game, is in use on typical TESTING. Viewing it on RustMaps is possible from this page: the same size and seed give the same map.
Which settings and rules apply on typical TESTING?
The name typical TESTING does not state a gather rate. Groups use the default maximum of 8 players. survival is the game mode, the normal mode where you gather, build and raid. Player versus player combat and raiding are enabled. A community server, it is found under the Community tab. VAC, Valve's anti-cheat, is enabled.
About the server
What version is typical TESTING running?
On Linux, typical TESTING operates Rust network protocol 2634 and build 167398. The protocol must match for you to join; Steam will update your game.
What is the performance like on typical TESTING?
The last 48 hours saw it average 240 server fps, never going under 240. The maximum entities it carried was 4,296, covering buildings, deployables and the rest. Its memory use reached 816 MB at most. What players experience as lag comes from low fps and a rising entity count.
Where can typical TESTING be found?
There is no region published by typical TESTING. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 15.204.83.240:21000.
Is typical TESTING currently online?
Currently offline is typical TESTING, last seen 36 hours ago. The uptime it gives suggests a restart around 2 days 3 hours ago. Across the last 6 full days, it was online for 58 of 144 hours, or 40%. The first time Top Rust Servers saw it was on 8 October 2026.
Wipe schedule
When does typical TESTING wipe?
The record holds too few wipes to determine typical TESTING's pattern. The monthly force wipe applies to every Rust server; the next one is on Thursday 5 November at 19:00 UTC. Its world was last replaced 8 days 4 hours ago.
How to join
What are the steps to join typical TESTING?
To connect, start Rust, hit F1, and enter client.connect 15.204.83.240:21000. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.