Rust Data LabData lab · live
Live readings Servers11,786 Players66,925 Populated3,511 Fresh wipes · 3h190 Sampled every 5 min

Element card · group Community · atomic number 15,333, its rank

Teste Local

Offline 177.191.235.202:28015 checked 9d ago

Join the experiment
Atomic mass · players now 0/ 10 0% full Room to join
7-day average0peak –
Rank · atomic number#15,333top 69%
Last wipe9d 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
15k10k15k20k19 Oct20 Oct22 Oct23 Oct25 Oct26 Oct

Top 69% 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

01234+0h+9h+19h+28h+38h+47h

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 15:40 UTC9d 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. 1 Ru Rusty Moose |E… 541
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 514 on average 541/ 525
  2. 2 Ru Rustoria.co - … 387
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 387/ 450
  3. 3 Ru Rusty Moose |E… 49
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 49/ 250
  4. 4 Ru Rustoria.co - … 50
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average 50/ 250
  5. 5 Ru Rustafied.com … 57
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 57/ 100
  6. 6 Ru Rustoria.co - … 165
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 241 on average 165/ 200

Quick answers

from the figures on this page

Settings and map

What map is in play on Teste Local?

A procedural map runs on Teste Local, generated by the game.

How is Teste Local configured, and what rules apply?

The name of Teste Local carries no gather rate. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. It appears under Community in the server browser. The VAC anti-cheat from Valve is enabled.

About the server

Which location is Teste Local based in?

Nothing about a region is published by Teste Local. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 177.191.235.202:28015 is the address it uses.

On what Rust version does Teste Local operate?

Rust network protocol 2634 and build 167781 on Windows is what Teste Local uses. Your game needs to match the protocol to join, and Steam updates it automatically.

Does Teste Local stay up, and how reliable is its uptime?

Currently offline, Teste Local was last seen 9 days 11 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. It first appeared to Rust Data Lab on 19 October 2026.

Wipe schedule

How often does a wipe happen on Teste Local, and at what time?

The record holds too few of Teste Local's wipes to show its rhythm. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. Counting back, the current world began 9 days 20 hours ago.

How does Teste Local look on the day of a wipe?

At their busiest, recent wipes averaged 1 players. The latest wipe's peak fell 0 hours after it began.

Lists and tags

What should you understand from the tags Teste Local carries?

gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 is the slot count; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): A region code has not been set here: that is the tag list Teste Local publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

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

You will find Teste Local on the following Rust Data Lab lists: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player counts

Against other Rust servers, where does Teste Local place?

Player hours over the last week put Teste Local at #15,333, inside the top 69% of ranked servers.

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

Teste Local is offline at the moment; the last sighting was 9 days 11 hours ago.

How to join

What is the way to join Teste Local?

Open the console with F1 in Rust and type client.connect 177.191.235.202:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp10
Max players 10 is the slot count.
ts8
Group limit Teams cap at 8, which is the game default.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs167781
Build The game build is 167781.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code A region code has not been set here.

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.