Rust Data

rustdata.spaceservers157.85.95.152:20001.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.95.152:20000 checked 9m ago

velocity test

moddedoxide

Connect

srv = rust.server("157.85.95.152:20001")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #4,510 # top 20%
last wipe 2d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75107:0016:0001:0010:0019:0004:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040007:0016:0001:0010:0019:0004:00

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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap21.5 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Sun 25 OctSat 3 Oct
00.511.52+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 25 Oct, 12:33 UTC2d ago 1 NaN running 1
1 Sat 3 Oct, 23:59 UTC24d ago 2 halved by day 1 21.5 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

1500 · seed 50000
Map of velocity test
map
Procedural Map
size
1500
seed
50000
Open on RustMaps

Server

srv.info()
address
157.85.95.152:20000
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
25 Oct 2026, 12:33 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 · 157 on average75/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average79/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average36/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average4/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average10/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does velocity test rank?

Over the last seven days velocity test sits at #4,510 on player hours, in the top 20% of ranked servers.

How many players does velocity test hold at once?

velocity test reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 07:00 UTC, mean 1 players.

Server facts

What does performance look like on velocity test?

Server fps over the last 48 hours averages 236; the floor is 213. Entity numbers reached 9,943, and that includes buildings, deployables and the rest. The memory field tops out at 2,471 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is velocity test on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by velocity test. Steam updates your game for you, but the protocol must match to join.

How reliable is velocity test, and is it online now?

Online is the state at the latest refresh for velocity test. The uptime it reports puts the last restart about 25 hours ago. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 13 September 2026.

In which location is velocity test hosted?

For velocity test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.95.152:20000 is its address.

Rules, settings, map

Which rules apply on velocity test, and what settings?

The name velocity test carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.

What is the map on velocity test?

velocity test runs a procedural map of size 1,500 with seed 50000, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does velocity test wipe, and on what schedule?

Too few wipes are on record for velocity test to reveal its rhythm. 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 2 days 17 hours ago.

What is wipe day on velocity test like?

Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.

Lists and tags

Which lists on Rust Data hold velocity test, and which filters?

These Rust Data lists include velocity test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meanings do the tags on velocity test hold?

The game's server browser reads these tags from velocity test: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

What is the way to join velocity test?

Enter client.connect 157.85.95.152:20000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players Slot count: 10.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 34,824 players 11,604 servers online