Rust Data

rustdata.spaceservers37.157.251.217:28014.ipynb

Run all rust-data · live

‹ All servers

Online 37.157.251.217:28015 checked 13m ago

German-Task-Force by Gamed!de

Connect

srv = rust.server("37.157.251.217:28014")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #12,429 # top 56%
last wipe 25d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123414:0023:0008:0017:0002:0011:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304014:0023:0008:0017:0002:0011: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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 3 OctThu 1 OctThu 1 Oct
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 Sat 3 Oct, 08:24 UTC25d ago 1 NaN running 0
1 Thu 1 Oct, 19:00 UTC FW26d ago 1 NaN 1.6 days 0
2 Thu 1 Oct, 00:34 UTC27d ago 0 NaN 0.8 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.

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

Map

6000 · seed 2147483647
Map of German-Task-Force by Gamed!de
map
Procedural Map
size
6000
seed
2147483647
Open on RustMaps

Server

srv.info()
address
37.157.251.217:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
3 Oct 2026, 08:24 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 average678/725
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average432/475
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 308 on average39/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 308 on average58/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 268 on average222/250
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 266 on average119/175

Quick answers

From the figures on this page.

Player counts

How does German-Task-Force by Gamed!de compare in the rankings?

Rank #12,429 on seven-day player hours for German-Task-Force by Gamed!de, within the top 56% of all ranked servers.

What population does German-Task-Force by Gamed!de carry?

Current row: 0 players on German-Task-Force by Gamed!de, against 10 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

What does performance look like on German-Task-Force by Gamed!de?

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

What Rust version does German-Task-Force by Gamed!de run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by German-Task-Force by Gamed!de. The protocol has to match before you can join, and Steam does the updating.

Is German-Task-Force by Gamed!de up, and what does its uptime show?

German-Task-Force by Gamed!de reports itself online at the current refresh. Count back 4 days 7 hours from its reported uptime to get the last restart. 168 of 168 hours up over the last 7 full days, or 100%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does German-Task-Force by Gamed!de sit?

For German-Task-Force by Gamed!de, 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 37.157.251.217:28015.

Rules, settings, map

Which rules apply on German-Task-Force by Gamed!de, and what settings?

No gather rate appears in the name: German-Task-Force by Gamed!de. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.

Which map has German-Task-Force by Gamed!de selected?

The game generates the map on German-Task-Force by Gamed!de: procedural, size 6,000, seed 2147483647. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

When does German-Task-Force by Gamed!de wipe, and how often?

No next wipe can be predicted for German-Task-Force by Gamed!de, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 25 days 4 hours ago, and that is the one in play.

On German-Task-Force by Gamed!de, what happens on wipe day?

The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain German-Task-Force by Gamed!de?

On Rust Data, German-Task-Force by Gamed!de appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on German-Task-Force by Gamed!de?

These tags are published by German-Task-Force by Gamed!de and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way into German-Task-Force by Gamed!de?

Enter client.connect 37.157.251.217: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 mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$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 72,836 players 11,736 servers online