Local RaidLab (flat, public build)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 5d ago · 83.190.130.89:28025

Abstract

We describe the public Rust server Local RaidLab (flat, public build), reached at 83.190.130.89:28025. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,437 of all servers, the top 69%. It last wiped 9d 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/4	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,437	top 69%
Last wipe	9d ago	no schedule published
Next wipe³	–	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.

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.

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

Measure	Value	Note
Usual gap	0.6 days	between real wipes
Wipe-day peak	0	players, last three wipes

Mon 19 OctSun 18 Oct

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Mon 19 Oct, 04:499d ago	0	–	running	0
Sun 18 Oct, 15:119d ago	0	–	0.6 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

Custom map, no picture published

Figure 5: The map: Custom Map.

Table 4: The server's published settings.

Address	`83.190.130.89:28025`
Region	–
Max players	4
Group limit	8, the default
Wipe schedule	–
Last wipe	19 Oct 2026, 04:49 UTC
Hostname	–
First seen	4 Oct 2026
Map	Custom Map
Size	–
Seed	–

7Similar servers

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

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

Server	Players
[EU] Builders Sanctuary 3.0 Creative \| Sandbox \| Minigames \|EU · groups of 8+ · 112 on average	194/999
[NA] Builders Sanctuary 3.0 Creative \| Sandbox \| Minigames \|NA · groups of 8+ · 91 on average	54/999
[AU] Rusticated.com - Creative Sandbox \| Build \| Never WipesOC · groups of 8+ · 52 on average	69/150
Atlas // CSL - Ranked \| Battlefield \| Aimtrain \| Scrims \| FFAEU · groups of 30+ · weekly · 37 on average	35/100
AQRUX RUST BUILD \| CREATIVE \| SANDBOXEU · groups of 8+ · monthly · 24 on average	34/100
KoalaKopters - Minicopter / Helicopter Training\|Arena\|Dogfightgroups of 8+ · 23 on average	33/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is Local RaidLab (flat, public build) based?

A region is not published by Local RaidLab (flat, public build). The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 83.190.130.89:28025.

A.2How reliable is Local RaidLab (flat, public build), and is it currently online?

Local RaidLab (flat, public build) is currently offline, with the last sighting 5 days 2 hours ago. Of the 168 hours in the last 7 full days, 24 were served, an availability of 14%. Its first appearance in Rust Statistics's records is 4 October 2026.

A.3What is the Rust version for Local RaidLab (flat, public build)?

Rust network protocol 2634 and build 167781 is the version that Local RaidLab (flat, public build) runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4On what cycle does Local RaidLab (flat, public build) wipe?

The record of Local RaidLab (flat, public build)'s wipes is not yet sufficient to establish its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 9 days 10 hours have passed since the current world was generated.

A.5What characterises wipe day on Local RaidLab (flat, public build)?

Across its recent wipes, the average peak population was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.6How does Local RaidLab (flat, public build) compare with other Rust servers in the rankings?

Ranked by player hours across seven days, Local RaidLab (flat, public build) holds #15,437, in the top 69% of all ranked servers.

A.7How would you characterise the player activity on Local RaidLab (flat, public build)?

At this moment Local RaidLab (flat, public build) is offline, having last been seen 5 days 2 hours ago. The seven-day average for this server is 0 players.

Tags and filters

A.8What do the tags associated with Local RaidLab (flat, public build) signify?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp4 (Max players): It offers 4 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs167781 (Build): Build 167781 is the one running; 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): The game is altered by plugins or settings, so it is listed as Modded, which Local RaidLab (flat, public build) 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.9Where can Local RaidLab (flat, public build) be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Local RaidLab (flat, public build) fits are: Modded Rust servers and Build and creative servers in Rust. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.10Under what rules and settings does Local RaidLab (flat, public build) operate?

Its name carries no gather rate for Local RaidLab (flat, public build). The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Players may raid and fight one another. The server browser lists it as Modded, where plugins or settings alter the game. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.

How to join

A.11What is the process for joining Local RaidLab (flat, public build)?

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

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

Tag	Meaning
Game
`gmrust`	Game mode. Rust survival, in its standard form.
`mp4`	Max players. It offers 4 slots.
`ts8`	Group limit. Teams are limited to 8, as the game defaults.
`v2634`	Protocol. Joining requires the same game version: protocol 2634.
`cs167781`	Build. Build 167781 is the one running.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. A region code has not been set.
Mods and access
`^o`	Oxide. Oxide (uMod), a plugin framework, runs on this server.
`^z`	Modded. The game is altered by plugins or settings, so it is listed as 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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Build server population list. ruststatistics.org/top-rust-build-servers.
[4]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.