Rust Server IndexCard catalogue of Rust servers

Holdings11,829 servers89,289 players82 fresh wipes

Call no.4432 On the shelf · online

velocity test

Online 157.85.95.152:20000 checked 1h ago

Subjects 1. modded2. oxide
Players now
1/ 10
10% full
7-day average
0
peak 2
Rank
#4,432
top 20%
Last wipeWiped25 OCT2026 · 3d 6h ago
3d ago · no schedule published
Next wipe
–
too few wipes seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.511.5219:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

010020030040019:0004:0013:0023:0008:0017: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.

Record sheet C · appended

Rank

daily · 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.

Record sheet D · loan terms

Wipe schedule

too few wipes seen yet

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

usual gap
21.5 daysbetween real wipes
wipe-day peak
2players, last three wipes
crowd held
0%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.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
25 OCT 2026Sun 25 Oct, 12:33 UTC3d ago
1 – running 1
3 OCT 2026Sat 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

ShockRust | Blue | NoLimitno group limit · 157 on average
205/ 500
EU
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
121/ 100
EU
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average
183/ 225
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average
126/ 700
EU
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average
19/ 200
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
50/ 1000
Reference desk

Quick answers

From the figures on this page.

Map and rules

Where can you read the rules and settings that apply on velocity test?

The name of velocity test does not state a gather rate. The group limit is 8 players, the game's default. The server runs survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. VAC, Valve's anti-cheat, is disabled.

Which map is in use on velocity test?

Size 1,500, seed 50000: the game generates the procedural map on velocity test. From this page you can view the map on RustMaps; the same size and seed give the same map.

Tags

On Rust Server Index, which lists and filters carry velocity test?

These lists on Rust Server Index take velocity test: Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which tags are attached to velocity test, and what do they stand for?

Filed under these tags, as published by velocity test and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp10 (Max players): Player cap: 10; ts8 (Group limit): Game default applies: teams of up to 8; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Plugins or changed settings put this under Modded. The top of this page shows three items from the tags: players at present, queue and world creation time.

Wipes and resets

What should you expect on velocity test when wipe day comes?

Its recent wipes averaged 2 players at peak. 0 hours into the latest wipe, the crowd reached its peak. The crowd held above half the peak until the next wipe in 0% of its recent wipes. By day 1 the crowd had fallen below half when it didn't hold.

How often is velocity test wiped, and on what schedule?

velocity test's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 3 days 6 hours.

Players and ranking

How is velocity test ranked compared with the rest?

On player hours over seven days, velocity test takes #4,432, within the top 20% of ranked servers.

How many players are on velocity test at the moment?

Filed under live counts: velocity test, 1 players on 10 slots at present. Filed under seven-day figures: an average of 0 players and a peak of 2. Over the last 48 hours, 16:00 UTC drew the highest average: 1 players.

Operator and status

Which Rust build is velocity test running?

Rust network protocol 2635 and build 168909, on Linux, is what velocity test runs. The protocol must match before you can join, and Steam takes care of updating it.

What is the uptime and current status of velocity test?

The server is live at this moment: velocity test. Its reported uptime gives the last restart as roughly 37 hours ago. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. On 13 September 2026 it was first seen by Rust Server Index.

What is performance like on velocity test?

The last 48 hours give an average of 237 server fps and a floor of 220. The entity count reached 9,955, covering buildings, deployables and all else in the world. Up to 2,553 MB of memory was in use. A climbing entity count and low fps are felt by players as lag.

What is the location of velocity test?

velocity test gives no region at all. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. You will reach it at 157.85.95.152:20000.

Connecting

What steps lead onto velocity test?

If you would rather use the console, press F1 in Rust and enter client.connect 157.85.95.152:20000. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, as standard.
mp10
Max players Player cap: 10.
ts8
Group limit Game default applies: teams of up to 8.
v2635
Protocol Your client must run protocol 2635 to connect.
cs168909
Build It runs build 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code The region code field is left empty.

Mods and access

^o
Oxide Oxide, also known as uMod, provides the plugin framework.
^z
Modded Plugins or changed settings put this 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.