Working its way up from the back of the class: #15,339 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 166 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··WW·WW
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 1, 17 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 22:27 UTC17d ago
1
–
running
0
Sat 10 Oct, 03:32 UTC19d ago
0
–
1.8 days
0
Thu 8 Oct, 03:21 UTC21d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does TAZ Rust | Servidor Teste sit?
TAZ Rust | Servidor Teste leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 170.81.87.230:28015 is the address to use.
Is TAZ Rust | Servidor Teste up, and how steady is its uptime?
You cannot join now: TAZ Rust | Servidor Teste is offline, last seen 7 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 7 October 2026.
Which Rust version is TAZ Rust | Servidor Teste running?
Rust network protocol 2634 and build 167398 on Windows is what TAZ Rust | Servidor Teste runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does TAZ Rust | Servidor Teste reset?
There is no next wipe to predict on TAZ Rust | Servidor Teste, as it wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 17 days 2 hours.
What should you expect from wipe day on TAZ Rust | Servidor Teste?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 17 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player numbers
Where does TAZ Rust | Servidor Teste place in the wider field of Rust servers?
Over the last seven days, TAZ Rust | Servidor Teste has #15,339 for player hours, in the top 69% of all ranked servers.
What does the population on TAZ Rust | Servidor Teste look like?
The last sighting of TAZ Rust | Servidor Teste was 7 days 5 hours ago, and it is offline right now.
Lists and filters
What do TAZ Rust | Servidor Teste's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp500 (Max players): Its slot count is 500; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): This runs on build 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags TAZ Rust | Servidor Teste publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature TAZ Rust | Servidor Teste?
Rust Server Score lists that include TAZ Rust | Servidor Teste: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is TAZ Rust | Servidor Teste set up, and what rules does it keep?
The name of TAZ Rust | Servidor Teste gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map TAZ Rust | Servidor Teste uses?
A procedural map of size 3,000 and seed 123456, generated by the game, is what TAZ Rust | Servidor Teste runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto TAZ Rust | Servidor Teste?
Enter client.connect 170.81.87.230:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp500
Max playersIts slot count is 500.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not 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.
A term to build on. Strongest in momentum (D); wipes are the one to work on (F).