Rust Data

rustdata.spaceservers92.4.133.57:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 92.4.133.57:28015 checked 5d ago

localbench

Connect

srv = rust.server("92.4.133.57:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,404 # top 69%
last wipe 5d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k22 Oct23 Oct24 Oct25 Oct26 Oct27 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 22:03 UTC5d ago 0 NaN running 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
92.4.133.57:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 22:15 UTC
hostname
–
first seen
22 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 511 on average564/625
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 340 on average36/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 337 on average68/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 316 on average281/325
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average116/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 261 on average122/150

Quick answers

From the figures on this page.

Population data

What position does localbench take in the server rankings?

Rank #15,404 on seven-day player hours for localbench, within the top 69% of all ranked servers.

How full does localbench run?

The current row shows localbench offline; the last response was 5 days ago. Over the last seven days it averaged 0 players.

About the server

Which Rust version is localbench on?

Rust network protocol 2634 and build 167781 on Linux is what localbench runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is localbench, and is it up?

localbench is offline at this refresh; the last response came 5 days ago. Over the last 4 full days the hours up number 0 of 96, 0%. Its earliest recorded date in Rust Data is 22 October 2026.

Which location does localbench run from?

For localbench, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 92.4.133.57:28015 is its address.

Settings and map

Which rules apply on localbench, and what settings?

You will not find a gather rate in the string localbench. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has localbench selected?

localbench runs a procedural map, which the game generates.

Wipes and dates

When does localbench wipe, and on what schedule?

The record for localbench holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 5 days ago, and that is the one in play.

On localbench, what happens on wipe day?

Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Tags, lists

Where does localbench appear among Rust Data lists and filters?

On Rust Data, localbench appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on localbench hold?

Read by the game's server browser, the tags localbench publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into localbench?

The manual route: launch Rust, F1, then client.connect 92.4.133.57:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players The server lists 10 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not 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.

Rust Data 63,710 players 11,765 servers online