Rust StatisticsWorking papers on every public Rust server · 32,059 players now

Local Benchmark

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 38d ago · 149.50.190.135:28015

Abstract

We describe the public Rust server Local Benchmark, reached at 149.50.190.135:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,010 of all servers. It last wiped 38d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/1100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,010no region published
Last wipe38d agono schedule published
Next wipe3–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 memory4. 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

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 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
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)PeakCrowdLastedBefore
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

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address149.50.190.135:28015
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe20 Sep 2026, 11:19 UTC
Hostname–
First seen20 Sep 2026
MapProcedural 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 player-run rust server list [2] and Rust wipe forecast [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 542 on average151/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average137/200
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average14/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 283 on average21/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average16/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average57/200

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does Local Benchmark have?

There is no region published for Local Benchmark. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 149.50.190.135:28015 is its address.

A.2How reliable is Local Benchmark, and is it currently online?

Right now, Local Benchmark is offline, and the last time it was seen was 38 days 18 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 20 September 2026 by Rust Statistics.

A.3What is the Rust version for Local Benchmark?

The version of Rust on Local Benchmark is network protocol 2633 and build 164530, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4When are wipes carried out on Local Benchmark?

Too few wipes by Local Benchmark have been recorded to determine the pattern. 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 world currently in use was created 38 days 18 hours ago.

Population

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

The seven-day player-hours ranking puts Local Benchmark at #15,010, within the top – of ranked servers.

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

At this moment Local Benchmark is offline, having last been seen 38 days 18 hours ago.

Tags, lists

A.7How should the tags on Local Benchmark be interpreted?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs164530 (Build): The game build is 164530; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set, which Local Benchmark publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

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

Rust community servers, measured are the Rust Statistics lists that Local Benchmark fits. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.9What are the settings and rules that govern Local Benchmark?

The name of Local Benchmark states no gather rate. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

A.10What is the map for Local Benchmark?

On Local Benchmark the terrain is procedural, built by the game itself.

Connection

A.11How do you connect to Local Benchmark?

Enter client.connect 149.50.190.135:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp1,ptrak,$r?,v2633,gmrust,cs164530,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp1Max players. The slot count is 1.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs164530Build. The game build is 164530.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. A region code has not been set.

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. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.