Working its way up from the back of the class: #15,196 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
27/ 100
F
Lost ground: down 7,037 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, top 90% in SA. Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·W···
·W··W··
·W·F··W
·W·W···
·W·W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 21:37 UTC, in 10h.
Its weekly schedule tag · low confidence
usual gap1.9 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2
Coming wipes
10hThu 29 Oct, 21:37 UTC
7d 8hThu 5 Nov, 19:00 UTCFW
14d 10hThu 12 Nov, 21:37 UTC
21d 10hThu 19 Nov, 21:37 UTC
28d 10hThu 26 Nov, 21:37 UTC
35d 8hThu 3 Dec, 19:00 UTCFW
42d 10hThu 10 Dec, 21:37 UTC
The first 48 hours of its last wipes
Thu 15 OctTue 13 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 21:37 UTC13d ago
0
–
running
0
Tue 13 Oct, 22:31 UTC15d ago
2
–
2 days
0
Thu 8 Oct, 06:02 UTC21d ago
1
halved by day 2
5.7 days
0
Tue 6 Oct, 21:39 UTC22d ago
1
–
1.3 days
1
Tue 6 Oct, 00:14 UTC23d ago
4
–
0.9 days
1
Sun 4 Oct, 16:27 UTC24d ago
4
–
1.3 days
0
Thu 1 Oct, 18:55 UTCFW27d ago
7
✓ held half
2.9 days
1
Tue 29 Sep, 21:14 UTC29d ago
6
–
1.9 days
0
Fri 25 Sep, 21:17 UTC33d ago
5
✓ held half
4 days
0
Tue 22 Sep, 21:18 UTC36d ago
5
✓ held half
3 days
2
Thu 17 Sep, 23:12 UTC41d ago
6
halved by day 2
4.9 days
1
Tue 15 Sep, 21:19 UTC43d ago
9
✓ held half
2.1 days
1
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
The SA tag on TESTE puts it in South America. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 178.132.198.136:31001.
How reliable is TESTE, and is it up?
The server is down: TESTE is offline now, with the last sighting 12 days 8 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
What Rust version is TESTE on?
Rust network protocol 2634 and build 167781 on Linux is what TESTE runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does TESTE wipe its map?
Too few wipes on TESTE are recorded to confirm the schedule, so its tag guides the prediction. Expect the next wipe on Thursday 29 October at 21:37 UTC. 22 days 13 hours have passed since this world was made. The tags carry a weekly wipe schedule.
What happens on TESTE when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 2.
Population
Where does TESTE place in the wider field of Rust servers?
Over the last seven days, TESTE has #15,196 for player hours, in the top 70% of all ranked servers and #200 in South America.
What does the population on TESTE look like?
The last sighting of TESTE was 12 days 8 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on TESTE?
The game's browser takes its cue from the tags TESTE has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; SA (South America): You will find it under South America in the browser. 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 TESTE?
These Rust Server Score lists count TESTE among them: Modded Rust servers, graded. It shows under the following filters on the server list: Region: South America; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Server rules
Which rules does TESTE enforce, and what are its settings?
Nothing in the name of TESTE states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. The server runs Valve's anti-cheat, VAC.
Can you tell me which map TESTE uses?
The game generates the procedural map on TESTE at size 4,000 with seed 325817136. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
What is the way to join TESTE?
To connect, start Rust, press F1, and type client.connect 178.132.198.136:31001. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^w,^v,SA,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
SA
South AmericaYou will find it under South America in the browser.
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 standing (F); wipes are the one to work on (F).