Server profile
Map Testing
Offline, with 0 of 2 players on; ranked #15,173 of every public Rust server, the top 70%. It last wiped 17d ago.
Offline 157.85.95.14:25931 checked 14d ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 70% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
No rhythm it keeps.
Its 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 wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The record
Wipes
Every wipe we saw, 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 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe schedule
What does Map Testing look like once wipe day arrives?
At their busiest, its recent wipes drew 2 players on average. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. The cases that did not hold saw the crowd fall below half by day 2.5.
How often does Map Testing wipe, and on which day?
There is no next wipe to predict: Map Testing wipes at irregular times. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. This world dates from 17 days 19 hours ago.
Server details
On what version does Map Testing currently run?
The Rust build is network protocol 2634 and build 167398, running on Linux, for Map Testing. Joining needs your game on the same protocol, which Steam updates for you.
What does uptime look like for Map Testing, and is it online?
The last sighting of Map Testing was 14 days 3 hours ago, and it is offline at present. It spent 0 of the last 7 full days' 168 hours up, 0% of the time. Rust Insights first logged this server on 13 September 2026.
In which location does Map Testing sit?
There is no region published for Map Testing. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. 157.85.95.14:25931 is where it answers.
Server tags
Which meanings sit behind the tags on Map Testing?
When the game's server browser reads Map Testing, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp2 (Max players): The slot count is 2; ts8 (Group limit): The game default applies: teams cap at 8; v2634 (Protocol): Your game must run the same version to join: the protocol is 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find the present player count, the queue and the world's creation time among the tags, and they are displayed at the top of this page.
Which Rust Insights filters and lists feature Map Testing?
The Rust Insights lists that carry Map Testing are Modded Rust servers, explained. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
How many players are on Map Testing right now, and how does that number move?
Map Testing was last seen 14 days 3 hours ago and is offline right now.
In the ranking of Rust servers, where does Map Testing place?
Player hours over seven days put Map Testing at #15,173, within the top 70% of the ranked field.
Settings and rules
What are the settings and rules for Map Testing?
Nothing about gather rate is given in the name of Map Testing. No group limit is set, so the game's default of 8 players applies. survival is the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Plugins or settings change the game, so it sits under Modded in the browser. It runs plugins, Oxide of them. The server has Valve's VAC anti-cheat switched on.
What is the map on Map Testing?
Map Testing runs a procedural map of size 3,000 with seed 163057, generated by the game. The same size and seed produce the same map, so from this page you can look at it on RustMaps. Read out, its map name is: Custom Map.
How to join
What is the way to join Map Testing?
To connect, start Rust and enter client.connect 157.85.95.14:25931 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.