RUST METRICSFlight deck · live data
Data live Servers11,882 Players96,098 Populated4,089 Fresh wipes 3 h164 Scan5 min
‹ All servers170.81.87.230:28015
Offline Full Queue Fresh wipe Wipe due No query

TAZ Rust | Servidor Teste

Offline 170.81.87.230:28015 checked 5d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,369top 70%
Last wipe15d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k7 Oct11 Oct15 Oct19 Oct23 Oct27 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.8 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Sun 11 OctSat 10 OctThu 8 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 22:27 UTC15d ago 1 – running 0
Sat 10 Oct, 03:32 UTC17d ago 0 – 1.8 days 0
Thu 8 Oct, 03:21 UTC19d ago 2 halved by day 1 2 days 1
Wed 7 Oct, 15:24 UTC20d ago 2 – 0.5 days 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on TAZ Rust | Servidor Teste?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 17 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 1 it fell below half when it didn't.

How often does TAZ Rust | Servidor Teste wipe, and when?

No next wipe can be predicted for TAZ Rust | Servidor Teste, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 15 days 17 hours ago.

Tags

How should you read the tags on TAZ Rust | Servidor Teste?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Game build reading: 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from TAZ Rust | Servidor Teste. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TAZ Rust | Servidor Teste?

On Rust Metrics, TAZ Rust | Servidor Teste sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does TAZ Rust | Servidor Teste sit in the rankings?

Player hours over seven days put TAZ Rust | Servidor Teste at #15,369, in the top 70% of all ranked servers.

How full does TAZ Rust | Servidor Teste get?

TAZ Rust | Servidor Teste is not responding; status offline, last seen 5 days 19 hours ago. A seven-day average of 0 players is the reading.

Server

Where does TAZ Rust | Servidor Teste sit?

Reading: location. TAZ Rust | Servidor Teste gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 170.81.87.230:28015.

What Rust version is TAZ Rust | Servidor Teste on?

Rust network protocol 2634 and build 167398 on Windows is the build TAZ Rust | Servidor Teste runs. Check: protocol. To join, your game must match; Steam handles the update.

Is TAZ Rust | Servidor Teste up, and how often does it stay up?

Check: connection. TAZ Rust | Servidor Teste is offline at this moment. Last contact was 5 days 19 hours ago. Uptime for the last 7 full days: 47 of 168 hours, or 28%. Reading: first seen 7 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on TAZ Rust | Servidor Teste?

Reading the name gives no gather rate for TAZ Rust | Servidor Teste. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on TAZ Rust | Servidor Teste?

Size 3,000 and seed 123456: the game generates the procedural map on TAZ Rust | Servidor Teste from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to TAZ Rust | Servidor Teste?

Press F1 in Rust and enter client.connect 170.81.87.230:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players The server holds 500 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Game build reading: 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.