Rust Data

rustdata.spaceservers170.81.87.230:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 170.81.87.230:28015 checked 7d ago

TAZ Rust | Servidor Teste

Connect

srv = rust.server("170.81.87.230:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak –
rank #15,339 # top 69%
last wipe 17d ago # no schedule published
next wipe – # no rhythm it keeps

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, measured since 8 Oct. 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
15k10k15k20k7 Oct11 Oct15 Oct20 Oct24 Oct28 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 11 Oct, 22:27 UTC17d ago 1 NaN running 0
1 Sat 10 Oct, 03:32 UTC18d ago 0 NaN 1.8 days 0
2 Thu 8 Oct, 03:21 UTC20d ago 2 halved by day 1 2 days 1
3 Wed 7 Oct, 15:24 UTC21d ago 2 NaN 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.

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

Map

3000 · seed 123456
Map of TAZ Rust | Servidor Teste
map
Procedural Map
size
3000
seed
123456
Open on RustMaps

Server

srv.info()
address
170.81.87.230:28015
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
12 Oct 2026, 00:56 UTC
hostname
–
first seen
7 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 · 555 on average161/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average97/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average15/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 286 on average16/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average14/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average17/200

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does TAZ Rust | Servidor Teste rank?

Over the last seven days TAZ Rust | Servidor Teste sits at #15,339 on player hours, in the top 69% of ranked servers.

How many players does TAZ Rust | Servidor Teste hold at once?

Offline now for TAZ Rust | Servidor Teste, with the last sample 7 days 4 hours ago.

Server data

What Rust version does TAZ Rust | Servidor Teste run?

Rust network protocol 2634 and build 167398 on Windows is what TAZ Rust | Servidor Teste runs. The protocol has to match before you can join, and Steam does the updating.

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

The latest sample has TAZ Rust | Servidor Teste offline, with a last sighting 7 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 7 October 2026.

Where does TAZ Rust | Servidor Teste sit?

There is no region published for TAZ Rust | Servidor Teste. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 170.81.87.230:28015.

Rules, settings, map

Which rules apply on TAZ Rust | Servidor Teste, and what settings?

No gather rate appears in the name: TAZ Rust | Servidor Teste. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.

What is the map on TAZ Rust | Servidor Teste?

Size 3,000, seed 123456: the procedural map on TAZ Rust | Servidor Teste, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

When does TAZ Rust | Servidor Teste wipe, and on what schedule?

TAZ Rust | Servidor Teste wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 17 days 1 hours ago.

What is wipe day on TAZ Rust | Servidor Teste like?

Across recent wipes the busiest point averaged 1 players. 17 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags and filters

Where does TAZ Rust | Servidor Teste appear among Rust Data lists and filters?

On Rust Data, TAZ Rust | Servidor Teste 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.

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

These tags are published by TAZ Rust | Servidor Teste and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): Slot count: 500; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): The server runs build 167398; 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.

How to join

What is the way to join TAZ Rust | Servidor Teste?

Enter client.connect 170.81.87.230:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp500
Max players Slot count: 500.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167398
Build The server runs build 167398.
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 36,352 players 11,696 servers online