velocity test
Online 157.85.95.152:20000 checked 12m 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 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. 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 25 Oct, 12:33 UTC2d ago | 1 | – | running | 1 |
| Sat 3 Oct, 23:59 UTC23d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 163 on average | 69 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 83 / 225 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 25 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 75 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 17 / 1000 |
Quick answers
from the figures on this pageWipe cycle
The wipe schedule for velocity test: what is it?
Too few wipes on record for velocity test to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 2 days 10 hours ago the current world was made.
On velocity test, what happens on wipe day?
Recent wipes averaged a busiest count of 2 players. Peak population for the latest wipe came 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The fall below half arrived by day 1 when it didn't hold.
Server details
Which location hosts velocity test?
No region is published by velocity test. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 157.85.95.152:20000.
Which Rust version is velocity test on?
Rust network protocol 2635 and build 168909 on Linux is the setup for velocity test. Your game must match the protocol to join, and Steam applies that update.
What uptime does velocity test show, and is it up?
The current status of velocity test is online. The uptime it reports puts the last restart at about 18 hours ago. 100% uptime over the last 7 full days, equal to 168 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.
Is performance on velocity test stable?
Server fps averaged 236 over the last 48 hours, with a floor of 213. At its highest the entity count was 9,860, including buildings, deployables and all else. At its highest, memory use was 2,471 MB. A climbing entity count and low fps are the lag players perceive.
Tags
What do velocity test's tags stand for?
The game's server browser reads the tags velocity test publishes: gmrust (Game mode): Survival in the standard Rust format; mp10 (Max players): Player slots: 10; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing, where plugins or settings change the game. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Where does velocity test appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include velocity test: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Player numbers
Against other Rust servers, how does velocity test compare?
Player hours for the last seven days place velocity test at #4,497, in the top 20% of the ranked field.
At what level does velocity test run its population?
velocity test holds 0 players of its 10 slots as of the latest update. The seven-day mean is 0 players, against a peak of 1. The 48-hour peak window is 02:00 UTC, at an average of 1 players.
Settings
What are the settings on velocity test, and its rules?
Gather rate is not mentioned in the name of velocity test. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. Oxide plugins are run. The server runs with VAC, Valve's anti-cheat, disabled.
The map on velocity test: which one is it?
velocity test uses a procedural map of size 1,500 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Connection
What is the way onto velocity test?
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.152:20000.