Rust Data

rustdata.spaceservers179.41.4.42:28016.ipynb

Run all rust-data · live

‹ All servers

Online 179.41.4.42:28015 checked 8m ago

GTZ Solitarios | Solo Duo | Wipe Mensual | x1

1x

Connect

srv = rust.server("179.41.4.42:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 1/30 # 3% full
7-day average 0 # peak 2
rank #7,151 # top 32%
last wipe 26d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75121:0000:0003:0006:0009:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510021:0000:0003:0006:0009:0012:00

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

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, 9 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 11:39 UTC26d ago 1 NaN running 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

4500 · seed 6738
Map of GTZ Solitarios | Solo Duo | Wipe Mensual | x1
map
Procedural Map
size
4500
seed
6738
Open on RustMaps

Server

srv.info()
address
179.41.4.42:28015
region
–
max players
30
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 11:39 UTC
hostname
–
first seen
13 Sep 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 · 543 on average653/725
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average448/475
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 308 on average37/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 308 on average49/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 268 on average214/250
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 266 on average135/175

Quick answers

From the figures on this page.

Population data

How does GTZ Solitarios | Solo Duo | Wipe Mensual | x1 compare in the rankings?

Over the last seven days GTZ Solitarios | Solo Duo | Wipe Mensual | x1 sits at #7,151 on player hours, in the top 32% of ranked servers.

How full does GTZ Solitarios | Solo Duo | Wipe Mensual | x1 run?

GTZ Solitarios | Solo Duo | Wipe Mensual | x1 reports 1 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 08:00 UTC is the busiest, at 1 players.

Server facts

What does performance look like on GTZ Solitarios | Solo Duo | Wipe Mensual | x1?

Server fps over the last 48 hours averages 77; the floor is 65. Buildings, deployables and all else in the world took the count as high as 112,823 entities. The memory field tops out at 3,133 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does GTZ Solitarios | Solo Duo | Wipe Mensual | x1 run?

Rust network protocol 2635 and build 168909 on Windows is what GTZ Solitarios | Solo Duo | Wipe Mensual | x1 runs. Steam updates your game for you, but the protocol must match to join.

How reliable is GTZ Solitarios | Solo Duo | Wipe Mensual | x1, and is it online now?

Online is the state at the latest refresh for GTZ Solitarios | Solo Duo | Wipe Mensual | x1. Count back 14 hours from its reported uptime to get the last restart. Uptime of 53% across the last 7 full days: 89 hours of 168. Rust Data logged it first on 13 September 2026.

Where does GTZ Solitarios | Solo Duo | Wipe Mensual | x1 sit?

For GTZ Solitarios | Solo Duo | Wipe Mensual | x1, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 179.41.4.42:28015.

Map and rules

What rules and settings are recorded for GTZ Solitarios | Solo Duo | Wipe Mensual | x1?

The name carries the figure: GTZ Solitarios | Solo Duo | Wipe Mensual | x1 runs 1x gather. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has GTZ Solitarios | Solo Duo | Wipe Mensual | x1 selected?

The game generates the map on GTZ Solitarios | Solo Duo | Wipe Mensual | x1: procedural, size 4,500, seed 6738. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does GTZ Solitarios | Solo Duo | Wipe Mensual | x1 wipe, and how often?

The record for GTZ Solitarios | Solo Duo | Wipe Mensual | x1 holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 2 hours ago.

On GTZ Solitarios | Solo Duo | Wipe Mensual | x1, what happens on wipe day?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 9 hours after it began.

Lists and tags

Which lists on Rust Data hold GTZ Solitarios | Solo Duo | Wipe Mensual | x1, and which filters?

These Rust Data lists include GTZ Solitarios | Solo Duo | Wipe Mensual | x1: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 1x.

How should you read the server tags on GTZ Solitarios | Solo Duo | Wipe Mensual | x1?

These tags are published by GTZ Solitarios | Solo Duo | Wipe Mensual | x1 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp30 (Max players): Slot count: 30; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is 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 into GTZ Solitarios | Solo Duo | Wipe Mensual | x1?

In Rust, F1 opens the console: type client.connect 179.41.4.42:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp30,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp30
Max players Slot count: 30.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is 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 76,905 players 11,770 servers online