jpbrandomvids

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 26d ago · 5.9.150.40:41355

Abstract

We describe the public Rust server jpbrandomvids, reached at 5.9.150.40:41355. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,950 of all servers, the top 69%. It last wiped 26d 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.

Measure	Value	Note
Players now	0/40	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,950	top 69%
Last wipe	26d ago	no schedule published
Next wipe³	–	no wipe 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.

No hourly history yet.

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 memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

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 2 Oct.

4Rank

The server stands in the top 69% 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

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

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

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
No wipe seen yet.

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 jpbrandomvids — Figure 4: The map: Procedural Map, size 2500, seed 1337. Open on RustMaps.

Table 3: The server's published settings.

Address	`5.9.150.40:41355`
Region	–
Max players	40
Group limit	8, the default
Wipe schedule	–
Last wipe	2 Oct 2026, 00:13 UTC
Hostname	–
First seen	2 Oct 2026
Map	Procedural Map
Size	2500
Seed	1337

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and next Rust wipe times [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 155 on average	185/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 24.10EU · groups of 8+ · weekly · 127 on average	120/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average	139/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average	138/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 87 on average	15/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	42/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is jpbrandomvids based?

There is no region published for jpbrandomvids. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 5.9.150.40:41355.

A.2What is the reliability of jpbrandomvids, and is it online?

Right now, jpbrandomvids is offline, and the last time it was seen was 26 days 11 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 2 October 2026 by Rust Statistics.

A.3What version of Rust is run on jpbrandomvids?

Rust network protocol 2634 and build 166494 is the version that jpbrandomvids runs, on Linux. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4What schedule does jpbrandomvids follow for wipes?

The record of jpbrandomvids's wipes is not yet sufficient to establish 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. The current world has been running for 26 days 12 hours.

Population

A.5How does jpbrandomvids compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts jpbrandomvids at #15,950, within the top 69% of ranked servers.

A.6How would you characterise the player activity on jpbrandomvids?

The last recorded sighting of jpbrandomvids was 26 days 11 hours ago; it is offline now.

Tags and filters

A.7How should the tags on jpbrandomvids be interpreted?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp40 (Max players): It offers 40 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which jpbrandomvids publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.8Where can jpbrandomvids be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that jpbrandomvids fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.9Which settings and rules are in force on jpbrandomvids?

The name of jpbrandomvids states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. The server has VAC on, Valve's anti-cheat.

A.10On which map does jpbrandomvids take place?

Size 2,500 and seed 1337 define the procedural, game-generated map on jpbrandomvids. Because size and seed determine the map, RustMaps can show it, linked from this page.

Connection

A.11How do you connect to jpbrandomvids?

Press F1 inside Rust to open the console and enter client.connect 5.9.150.40:41355. 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 mp40,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Survival on standard Rust rules.
`mp40`	Max players. It offers 40 slots.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2634`	Protocol. Joining requires the same game version: protocol 2634.
`cs166494`	Build. The game build is 166494.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. No region code is set.
Mods and access
`^o`	Oxide. The plugin framework in use is Oxide (uMod).
`^z`	Modded. 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]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.