Rust Data

rustdata.spaceservers179.94.49.6:28017.ipynb

Run all rust-data · live

‹ All servers

Offline SA 179.94.49.6:28015 checked 15d ago

TESTE SERVER

trio weekly wipes vanillamoddedoxide

Connect

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

Right now

srv.summary()
players now 0/?
7-day average 0 # peak –
rank #15,281 # top 71% · #202 in SA
last wipe 16d ago # weekly schedule
next wipe 4d 23h # Tue 3 Nov, 11:17 UTC

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 11 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
15k10k15k20k11 Oct13 Oct15 Oct16 Oct18 Oct20 Oct

Top 71% of all ranked servers, top 90% in SA, and #520 of the trio servers (top 82%). Ranked on player hours over the last seven days.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Tuesday 3 November, 11:17 UTC, in 4d 23h. # Its weekly schedule tag · low confidence

wipe-day peak1players, last three wipes

Coming wipes

inatkind
04d 23hTue 3 Nov, 11:17 UTCwipe
17d 6hThu 5 Nov, 19:00 UTCFW force wipe
211d 23hTue 10 Nov, 11:17 UTCwipe
318d 23hTue 17 Nov, 11:17 UTCwipe
425d 23hTue 24 Nov, 11:17 UTCwipe
532d 23hTue 1 Dec, 11:17 UTCwipe
635d 6hThu 3 Dec, 19:00 UTCFW force wipe
739d 23hTue 8 Dec, 11:17 UTCwipe

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 13 Oct, 11:17 UTC16d ago 1 NaN running 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.

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

Map

3450 · seed 1337
Map of TESTE SERVER
map
Custom Map
size
3450
seed
1337

Server

srv.info()
address
179.94.49.6:28015
region
SA
max players
–
group limit
trio
wipe schedule
weekly
last wipe
13 Oct 2026, 11:17 UTC
hostname
–
first seen
10 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[BR/LATAM] TERRA HOSTIL VANILLA | SOLO/ DUO/ TRIO |SA · trio · weekly · 28 on average9/250
1[LATAM] SOLO NOOB Solo/Duo/Trio | 26/10 WipeSA · trio · weekly · 8 on average1/200
2[LATAM] SOLO NOOB X2 Solo/Duo/Trio | 27/10 WipeSA · trio · 2x · weekly · 63 on average2/100
3[BR/LATAM] EXTREME 2X | SOLO/DUO/TRIO | WIPE 28/10SA · trio · 2x · weekly · 46 on average16/100
4[BR/LATAM] GUERRA FRIA 2X TRIO 28/10 [vK.gg]SA · trio · 2x · weekly · 17 on average6/125
5[BR/LATAM] TERRA HOSTIL 2X | SOLO/ DUO/ TRIO |SA · trio · 2x · weekly · 11 on average3/200

Quick answers

From the figures on this page.

Population data

What position does TESTE SERVER take in the server rankings?

Ranked #15,281 on seven-day player hours, TESTE SERVER is #202 in South America and in the top 71% of all ranked servers. Its position in the trio group is #520.

What population does TESTE SERVER carry?

Offline now for TESTE SERVER, with the last sample 15 days 15 hours ago.

Server data

Which Rust version is TESTE SERVER on?

The build is Rust network protocol 2634 and build 167781 on Windows, run by TESTE SERVER. Joining needs the same protocol on your game; Steam handles the update.

How reliable is TESTE SERVER, and is it online now?

The latest sample has TESTE SERVER offline, with a last sighting 15 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 10 October 2026.

Which location does TESTE SERVER run from?

In South America, TESTE SERVER lists itself, using the SA tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 179.94.49.6:28015.

Map and rules

What rules and settings are recorded for TESTE SERVER?

No gather rate appears in the name: TESTE SERVER. Up to 3 players may share a group (trio). Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. VAC is running: Valve's anti-cheat is on.

Which map has TESTE SERVER loaded?

TESTE SERVER runs a procedural map of size 3,450 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Custom Map.

Wipe data

When does TESTE SERVER wipe, and on what schedule?

The prediction follows the tag, because TESTE SERVER's wipes on record are too few to confirm the schedule. Tuesday 3 November at 11:17 UTC is when the next wipe is due. The world it runs now was generated 16 days ago. A weekly wipe schedule is published in its tags.

On TESTE SERVER, what happens on wipe day?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Which lists on Rust Data hold TESTE SERVER, and which filters?

On Rust Data, TESTE SERVER appears in these lists: Modded Rust servers and Trio Rust servers. It appears under 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: Trio; Wipe schedule: Weekly.

Which meanings do the tags on TESTE SERVER hold?

The game's server browser reads these tags from TESTE SERVER: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): The server lists 0 slots; ts3 (Group limit): No team may exceed 3; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^w (Weekly): Wipes run weekly; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; SA (South America): In the server browser it sits under South America. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into TESTE SERVER?

Enter client.connect 179.94.49.6: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 mp0,ptrak,$r?,v2634,^w,^v,SA,gmrust,cs167781,ts3,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp0
Max players The server lists 0 slots.
ts3
Group limit No team may exceed 3.
v2634
Protocol To join, your game must run protocol 2634.
cs167781
Build Build number: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Wipes run weekly.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

SA
South America In the server browser it sits 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.

Rust Data 65,727 players 11,762 servers online