Map Testing
Offline 157.85.95.14:25931 checked 13d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 11 Oct, 08:15 UTC17d ago | 1 | – | running | 1 |
| Fri 9 Oct, 17:17 UTC19d ago | 2 | – | 1.6 days | 0 |
| Thu 1 Oct, 18:33 UTC FW27d ago | 2 | halved by day 4 | 7.9 days | 1 |
| Tue 15 Sep, 19:32 UTC43d ago | 1 | halved by day 1 | 16 days | 0 |
| Mon 14 Sep, 18:51 UTC44d ago | 2 | – | 1 days | 0 |
| Mon 14 Sep, 09:19 UTC44d ago | 2 | – | 0.4 days | 1 |
| Sun 13 Sep, 12:53 UTC45d ago | 2 | – | 0.9 days | 0 |
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| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 157 on average | 94 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 102 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 82 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 28 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18 / 1000 |
Quick answers
from the figures on this pageWipe cycle
The wipe schedule for Map Testing: what is it?
The next wipe on Map Testing cannot be predicted, because it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The current world dates from 17 days 12 hours.
On Map Testing, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. The highest player count on the latest wipe arrived 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the other cases the crowd dropped below half by day 2.5.
Server
Which location hosts Map Testing?
A region is not published by Map Testing. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 157.85.95.14:25931.
Which Rust version is Map Testing on?
The platform is Linux, with Rust network protocol 2634 and build 167398 running on Map Testing. Your game must match the protocol to join, and Steam applies that update.
How reliable is Map Testing, and is it online now?
The current status is offline for Map Testing, with the last sighting 13 days 21 hours ago. Uptime over the last full days (7) was 0%, or 0 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.
Lists and tags
What do Map Testing's tags stand for?
gmrust (Game mode): Rust survival, standard ruleset; mp2 (Max players): Capacity of 2 slots; ts8 (Group limit): Team cap of 8, the stock game setting; v2634 (Protocol): To join, your game version must match protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded are the tags Map Testing publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does Map Testing appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists Map Testing fits are: Modded Rust servers: live data. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player numbers
Against other Rust servers, how does Map Testing compare?
Player hours for the last seven days place Map Testing at #15,173, in the top 70% of the ranked field.
How many players does Map Testing carry?
Map Testing is offline at this refresh; the last contact was 13 days 21 hours ago.
Settings
What are the settings on Map Testing, and its rules?
No gather rate is given in the name of Map Testing. No custom group limit: 8 players is the standard. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. Plugins from Oxide are in use. Anti-cheat status: VAC on.
The map on Map Testing: which one is it?
The game generates a procedural map of size 3,000 with seed 163057 for Map Testing. Size and seed fix the map, so a RustMaps view is available from this page. Named map: Custom Map.
Connection
What is the way onto Map Testing?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 157.85.95.14:25931.