Element card · group Community · atomic number 13,967, its rank

Local Test

Offline 136.33.51.113:28015 checked 26d ago

Join the experiment

Launch Rust and join

Atomic mass · players now 1/ 500 0% full Room to join

7-day average0peak –

Rank · atomic number#13,967top 59%

Last wipe26d agono schedule published

Next wipe–too few wipes seen yet

Result 01

Players

Method

Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.

Result

No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method

Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.

Result

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region

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

Reaction kinetics

Wipe schedule

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.

wipe-day peak1players, last three wipes

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.

Reaction log

Wipes

newest first

Wiped	Peak	Crowd	Lasted	Players before
Thu 1 Oct, 14:34 UTC26d ago	1	–	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.

Similar servers

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

1 Ru Rusty Moose |E… 440
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 520 on average 440/ 525
2 Ru Rustoria.co - … 25
Rustoria.co - EU Main EU · groups of 16+ · weekly · 336 on average 25/ 250
3 Ru Rusty Moose |E… 45
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 333 on average 45/ 250
4 Ru Rustoria.co - … 201
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average 201/ 275
5 Ru Rustoria.co - … 76
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 279 on average 76/ 200
6 Ru Rustafied.com … 88
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 263 on average 88/ 150

Quick answers

from the figures on this page

Settings and map

What rules has Local Test set, and what settings are in force?

Nothing in the name of Local Test gives a gather rate. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. Raids and player fights are part of play here. It appears under Community in the server browser. The VAC anti-cheat from Valve is enabled.

Server details

Which location is Local Test based in?

There is no region on record for Local Test. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. You will find it at 136.33.51.113:28015.

On what Rust version does Local Test operate?

On Windows, Local Test is running Rust network protocol 2633 and build 165217. The protocol must match for you to join; Steam will update your game.

How reliably does Local Test stay online?

Local Test is not online at the moment; the last sighting was 26 days 7 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. On 1 October 2026, Rust Data Lab saw it for the first time.

Wipe days

What is the wiping pattern on Local Test?

Local Test's wipe history on record is too thin yet to tell its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 26 days 9 hours ago.

On Local Test, what happens when wipe day arrives?

Recent wipes on average reached 1 players at their busiest. The latest wipe's peak fell 0 hours after it began.

Tags, lists

How should you read the tags on Local Test?

gmrust (Game mode): Standard Rust survival is the game here; mp500 (Max players): 500 is the slot count; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): The server runs protocol 2633, so your game needs the same version; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): No region code is set: that is the tag list Local Test publishes, and the game's server browser reads it. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Where among the Rust Data Lab lists and filters does Local Test come up?

You will find Local Test on the following Rust Data Lab lists: Rust community servers, measured. 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.

Player numbers

What position does Local Test hold among Rust servers?

Local Test sits at #13,967 for seven-day player hours, placing it in the top 59% of ranked servers.

What does the current player count on Local Test tell you?

Local Test is offline at the moment; the last sighting was 26 days 7 hours ago.

Connection

What steps get you onto Local Test?

In Rust, press F1 and enter client.connect 136.33.51.113:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8

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.