Fig. 1Players on TESTERG-S15196-01 · Sheet 1 of 10
Fig. 2
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.
Fig. 2FPS, entities and memoryRG-S15196-02 · Sheet 2 of 10
Fig. 3
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.
Fig. 3Rank on player hours, dailyRG-S15196-03 · Sheet 3 of 10
Schedule
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 6d 19h.
The force wipe · high 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
6d 19hThu 5 Nov, 19:00 UTCFW
13d 21hThu 12 Nov, 21:37 UTC
20d 21hThu 19 Nov, 21:37 UTC
27d 21hThu 26 Nov, 21:37 UTC
34d 19hThu 3 Dec, 19:00 UTCFW
41d 21hThu 10 Dec, 21:37 UTC
The first 48 hours of its last wipes
Thu 15 OctTue 13 OctThu 8 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
ScheduleExpected wipesRG-S15196-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 21:37 UTC14d ago
0
–
running
0
Tue 13 Oct, 22:31 UTC16d 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 UTC23d ago
1
–
1.3 days
1
Tue 6 Oct, 00:14 UTC23d ago
4
–
0.9 days
1
Sun 4 Oct, 16:27 UTC25d ago
4
–
1.3 days
0
Thu 1 Oct, 18:55 UTCFW28d ago
7
held half
2.9 days
1
Tue 29 Sep, 21:14 UTC30d ago
6
–
1.9 days
0
Fri 25 Sep, 21:17 UTC34d ago
5
held half
4 days
0
Tue 22 Sep, 21:18 UTC37d ago
5
held half
3 days
2
Thu 17 Sep, 23:12 UTC42d ago
6
halved by day 2
4.9 days
1
Tue 15 Sep, 21:19 UTC44d 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.
Table 1Wipe logRG-S15196-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is TESTE online, and what uptime has been recorded?
Last seen 12 days 20 hours ago; right now TESTE is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. First seen by Rust Graphs on 13 September 2026.
2.
In which location is TESTE hosted?
The SA tag is how TESTE lists itself in South America. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 178.132.198.136:31001 is its address.
3.
On which Rust version is TESTE running?
On Linux, TESTE runs Rust network protocol 2634 and build 167781. The same protocol is required for joining, and Steam updates your game to it.
Population
4.
How many players are plotted on TESTE?
No response from TESTE; the server was last seen 12 days 20 hours ago.
5.
What rank has been recorded for TESTE?
Across seven days, player hours give TESTE #15,196 globally and #200 in South America, a top 70% position among ranked servers.
Wipe data
6.
On TESTE, what does the data show for wipe day?
At their busiest, its recent wipes drew 1 players on average. At 0 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 2.
7.
What wipe schedule has been recorded for TESTE?
Too few of TESTE's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world has been in use since 23 days 2 hours ago. The tags state a weekly wipe schedule.
Rules and settings
8.
Which rules and settings are recorded for TESTE?
No gather rate is stated in the name of TESTE. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Its own label is vanilla, meaning no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat: VAC, from Valve, is on.
9.
What is the map for TESTE?
Seed 325817136 and size 4,000 define the procedural map TESTE generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Lists and filters
10.
Where does TESTE appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry TESTE are: Modded Rust servers. It is returned by these 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.
11.
On TESTE, what is meant by each tag?
The game's server browser reads these tags from TESTE: gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): The slot count is 100; ts8 (Group limit): The default team size of 8 applies; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): 167781 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^w (Weekly): A wipe occurs every week; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; SA (South America): The browser's listing places it under South America. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Connect
12.
What is the way to connect to TESTE?
Connect with client.connect 178.132.198.136:31001: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
NotesAnswered from the figuresRG-S15196-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^w,^v,SA,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp100
Max playersThe slot count is 100.
ts8
Group limitThe default team size of 8 applies.
v2634
ProtocolJoin only if your game is on protocol 2634.
cs167781
Build167781 is the game build.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeThe region code field is empty.
Wipe schedule
^w
WeeklyA wipe occurs every week.
Difficulty
^v
VanillaNo changed rates, kits or rules: the game as Facepunch ships it.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
Region
SA
South AmericaThe browser's listing places it under South America.
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.
KeyTag string decodedRG-S15196-10 · Sheet 10 of 10