Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO D SRV11,718online PAX47,661playing OCC3,204with players WIPED 3H101
COMCommunity traffic
Callsign

TZA15339

TAZ Rust | Servidor Teste

Offline 170.81.87.230:28015 checked 7d ago

Clearance · join
Players now 0/ 500 0% full
7-day average0peak –
Rank#15,339top 69%
Last wipe16d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k7 Oct11 Oct15 Oct20 Oct24 Oct28 Oct

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

Flight 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.

Wipes

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

Nearby traffic

Similar servers

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

  1. 01COM
    Callsign RST015EU · groups of 12+ · weekly · 560 on average Rusty Moose |EU Mondays|
    Players 249/275
  2. 02COM
    Callsign RST015EU · groups of 12+ · monthly · 319 on average Rustoria.co - EU East Long
    Players 166/200
  3. 03COM
    Callsign RST015EU · groups of 12+ · weekly · 292 on average Rusty Moose |EU Main|
    Players 30/250
  4. 04COM
    Callsign RST015EU · groups of 16+ · weekly · 291 on average Rustoria.co - EU Main
    Players 18/250
  5. 05COM
    Callsign RST018EU · groups of 16+ · weekly · 274 on average Rustafied.com - EU Friday
    Players 39/100
  6. 06COM
    Callsign RST015EU · groups of 12+ · biweekly · 251 on average Rustoria.co - EU East Medium
    Players 50/200
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

On Rust Tracker, TAZ Rust | Servidor Teste sits in these lists: Community servers, no tags. These filters surface it on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which tags does TAZ Rust | Servidor Teste carry, and what do they mean?

Listed for the server browser to read, TAZ Rust | Servidor Teste publishes these tags: gmrust (Game mode): Rust survival, standard mode; mp500 (Max players): Slots: 500; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167398 (Build): Build: 167398; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Schedule

What happens on TAZ Rust | Servidor Teste on wipe day?

The average peak across recent wipes: 1 players. The peak on the latest wipe came 17 hours after it. Half the peak was held until the next wipe in 0% of its recent wipes. By day 1 the crowd dropped below half where it did not hold.

On what schedule does TAZ Rust | Servidor Teste wipe?

Wipe times at TAZ Rust | Servidor Teste are irregular, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. This world has been running 16 days 23 hours.

Server Details

How reliable is TAZ Rust | Servidor Teste, and is it online now?

Tracking shows TAZ Rust | Servidor Teste offline as of now, last seen 7 days 1 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. Rust Tracker logged it first on 7 October 2026.

Which Rust version is confirmed on TAZ Rust | Servidor Teste?

Confirmed for TAZ Rust | Servidor Teste: Rust network protocol 2634 and build 167398, Windows. To join, your game must be on the same protocol; Steam handles the update.

Which location is TAZ Rust | Servidor Teste in?

Nothing on region from TAZ Rust | Servidor Teste; none is published. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 170.81.87.230:28015.

Player Count

Is TAZ Rust | Servidor Teste busy?

Offline now for TAZ Rust | Servidor Teste, last seen 7 days 1 hours ago. Seven-day average for this server: 0 players.

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

Seven-day player hours put TAZ Rust | Servidor Teste at #15,339, within the top 69% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on TAZ Rust | Servidor Teste?

Nothing in TAZ Rust | Servidor Teste's name states a gather rate. The game's default applies: groups can have up to 8 players. It runs survival, gather, build, raid, as the game intends. Fighting and raiding between players are on. Listed under Community in the server browser, it is a community server. VAC is on, Valve's anti-cheat.

Which map is confirmed for TAZ Rust | Servidor Teste?

A procedural map of size 3,000 runs on TAZ Rust | Servidor Teste, generated by the game from seed 123456. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

Which steps join TAZ Rust | Servidor Teste?

To connect: start Rust, press F1, enter client.connect 170.81.87.230:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp500
Max players Slots: 500.
ts8
Group limit Teams cap at 8; this is the game default.
v2634
Protocol Your game must be on protocol 2634 to connect.
cs167398
Build Build: 167398.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code No region code is 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.