Rust StatisticsWorking papers on every public Rust server · 34,648 players now

velocity test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 12m ago · 157.85.95.152:20000

Abstract

We describe the public Rust server velocity test, reached at 157.85.95.152:20000. At the last check it held 0 of 10 places, against a seven-day mean of 0 and a peak of 11. It ranks #4,516 of all servers, the top 20%. It last wiped 2d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/100% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#4,516top 20%
Last wipe2d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75105:0014:0023:0009:0018:0003:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
010020030040005:0014:0023:0009:0018:0003:00
Figure 2: 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.

4Rank

The server stands in the top 20% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap21.5 daysbetween real wipes
Wipe-day peak2players, last three wipes
Crowd held0%else halves by day 1
Sun 25 OctSat 3 Oct
00.511.52+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sun 25 Oct, 12:332d ago 1 – running 1
Sat 3 Oct, 23:5924d ago 2 halved by day 1 21.5 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of velocity test
Figure 5: The map: Procedural Map, size 1500, seed 50000. Open on RustMaps.
Table 4: The server's published settings.
Address157.85.95.152:20000
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe25 Oct 2026, 12:33 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size1500
Seed50000

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 159 on average42/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average134/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average53/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average23/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average4/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average7/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does velocity test perform well?

The server fps averaged 236 over the last 48 hours, never dropping below 213. The highest number of entities it carried was 9,943, comprising buildings, deployables and all other objects. Its highest memory usage was 2,471 MB. Players experience lag when fps is low and the entity count is rising.

A.2In which location is velocity test based?

There is no region published for velocity test. Rust Statistics does not look up the machine's location; it shows where the server says it is. 157.85.95.152:20000 is its address.

A.3How reliable is velocity test, and is it currently online?

velocity test is online at this time. Based on the uptime it reports, the last restart occurred about 24 hours ago. Its uptime over the last full days (7 days) was 100%, with 168 of 168 hours online. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What version of Rust is run on velocity test?

The version of Rust on velocity test is network protocol 2635 and build 168909, and the operating system is Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5On what cycle does velocity test wipe?

There are not yet enough recorded wipes for velocity test to reveal its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. 2 days 15 hours have passed since the current world was generated.

A.6What characterises wipe day on velocity test?

Across its recent wipes, the average peak population was 2 players. The peak on the latest wipe came 0 hours after it began. Half the peak was sustained until the next wipe in 0% of recent wipes. In the other cases, the population fell below half by day 1.

Population

A.7How does velocity test compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts velocity test at #4,516, within the top 20% of ranked servers.

A.8What is the population level of velocity test?

On velocity test, 0 of the 10 slots are occupied at present. Averaged over the last seven days: 0 players; the same period peaks at 1. Of the last 48 hours, the peak hour falls at 05:00 UTC, with an average of 1 players.

Tags, lists

A.9What is the meaning of the tags on velocity test?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): It offers 10 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game, which velocity test publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can velocity test be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that velocity test fits. 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 3 days.

Settings and map

A.11Under what rules and settings does velocity test operate?

No gather rate appears in the name of velocity test. The group cap is 8 players, which is the default in the game. survival is the game mode here; gather, build and raid: the standard game. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. The plugin count is Oxide. VAC is inactive: the anti-cheat from Valve is off.

A.12What map is in use on velocity test?

Size 1,500 and seed 50000 define the procedural, game-generated map on velocity test. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

Connection

A.13What is the process for joining velocity test?

Press F1 inside Rust to open the console and enter client.connect 157.85.95.152:20000. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp10Max players. It offers 10 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. This server runs game build 168909.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. Modded listing: plugins or settings modify 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.