velocity test
Online 157.85.95.152:20000 checked 1h ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not 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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 25 Oct, 12:33 UTC3d ago | 1 | – | running | 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.
Quick answers
Population
How does velocity test rank against other Rust servers?
Over the past week it ranks #4,432 for player hours, which puts velocity test in the top 20% of all ranked servers.
How busy is velocity test?
Of its 10 slots, velocity test is using 1 right now. Seven days of counting give an average of 0 players and a peak of 2. Look at the last 48 hours and 16:00 UTC stands out: it averaged 1 players.
Tags
What do the server tags on velocity test mean?
The game's server browser reads the tags velocity test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): This server appears under Modded because plugins or settings alter the game. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include velocity test?
On Rust Population, velocity test is filed under these lists: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Wipe schedule
What does wipe day look like on velocity test?
The busiest point of its recent wipes averaged 2 players. 0 hours after the latest wipe the crowd peaked. In 0% of recent wipes, half the peak was held until the next wipe. In those that did not hold, the fall below half came by day 1.
What is the wipe schedule on velocity test?
Too few wipes are on record for velocity test to show its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 3 days 5 hours ago, that is how long the current world has stood.
Map and rules
Which map does velocity test run?
The map on velocity test is procedural, made by the game at size 1,500 from seed 50000. Size and seed together fix the map, so you can view it on RustMaps from this page.
What are the rules and settings on velocity test?
No gather rate appears in the name of velocity test. The group limit is 8 players, which is the default. survival is what it runs, raid, build and gather: the standard game. Combat between players, raids included, is permitted. The server browser files it under Modded, where plugins or settings alter the game. You will find Oxide running as plugins. The anti-cheat VAC from Valve is disabled.
Server details
Which version of Rust does velocity test run?
The setup is Rust network protocol 2635 and build 168909 on Linux for velocity test. Your game needs the same protocol to join; Steam takes care of updating it.
Does velocity test run smoothly?
It ran at 237 server fps on average over the last 48 hours, and never went below 220. Up to 9,955 entities were present, counting buildings, deployables and everything else. Up to 2,553 MB of memory was used. What players experience as lag comes from low fps and a rising entity count.
Is velocity test online, and how reliable is it?
Right now, velocity test is online. About 37 hours ago, it restarted, according to its uptime. Over the last 7 full days, 168 of 168 hours were online, or 100%. On 13 September 2026, Rust Population saw it for the first time.
Where is velocity test located?
A region is not published by velocity test. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 157.85.95.152:20000.
Getting in
How do I join velocity test?
Open the console with F1 in Rust and enter client.connect 157.85.95.152:20000. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.