Rust Data

rustdata.spaceservers157.85.95.14:25932.ipynb

Run all rust-data · live

‹ All servers

Offline 157.85.95.14:25931 checked 14d ago

Map Testing

moddedoxide

Connect

srv = rust.server("157.85.95.14:25932")
print(srv.connect_command)

Right now

srv.summary()
players now 0/2 # 0% full
7-day average 0 # peak –
rank #15,173 # top 70%
last wipe 17d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep26 Sep2 Oct9 Oct15 Oct21 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2.5

The first 48 hours of its last wipes

Sun 11 OctFri 9 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 11 Oct, 08:15 UTC17d ago 1 NaN running 1
1 Fri 9 Oct, 17:17 UTC19d ago 2 NaN 1.6 days 0
2 Thu 1 Oct, 18:33 UTC FW27d ago 2 halved by day 4 7.9 days 1
3 Tue 15 Sep, 19:32 UTC43d ago 1 halved by day 1 16 days 0
4 Mon 14 Sep, 18:51 UTC44d ago 2 NaN 1 days 0
5 Mon 14 Sep, 09:19 UTC44d ago 2 NaN 0.4 days 1
6 Sun 13 Sep, 12:53 UTC45d ago 2 NaN 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.

display(srv.map, srv.info())

Map

3000 · seed 163057
Map of Map Testing
map
Custom Map
size
3000
seed
163057

Server

srv.info()
address
157.85.95.14:25931
region
–
max players
2
group limit
8, the default
wipe schedule
–
last wipe
11 Oct 2026, 09:04 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 153 on average33/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average122/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average53/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average13/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average3/1000

Quick answers

From the figures on this page.

Player counts

What position does Map Testing take in the server rankings?

Over the last seven days Map Testing sits at #15,173 on player hours, in the top 70% of ranked servers.

How full does Map Testing run?

The current row shows Map Testing offline; the last response was 14 days 4 hours ago.

Server data

What is the Rust version on Map Testing?

Version Rust network protocol 2634 and build 167398 on Linux is reported by Map Testing. The protocol has to match before you can join, and Steam does the updating.

Is Map Testing up, and what does its uptime show?

Map Testing is offline at this refresh; the last response came 14 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 13 September 2026.

In which location is Map Testing hosted?

There is no region published for Map Testing. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 157.85.95.14:25931.

Settings and map

Which settings and rules does Map Testing run?

No gather rate appears in the name: Map Testing. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has Map Testing selected?

The game generates the map on Map Testing: procedural, size 3,000, seed 163057. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.

Wipes and dates

When does Map Testing wipe, and how often?

No next wipe can be predicted for Map Testing, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 17 days 19 hours ago.

On Map Testing, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 2.5.

Lists and tags

Where does Map Testing appear among Rust Data lists and filters?

On Rust Data, Map Testing appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on Map Testing hold?

These tags are published by Map Testing and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way into Map Testing?

The manual route: launch Rust, F1, then client.connect 157.85.95.14:25931. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp2,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp2
Max players The server lists 2 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167398
Build Recorded game build: 167398.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 32,367 players 11,640 servers online