Rust Data

rustdata.spaceservers207.174.41.154:27015.ipynb

Run all rust-data · live

‹ All servers

Online 207.174.41.154:28015 checked 8m ago

Terabit.io

Connect

srv = rust.server("207.174.41.154:27015")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak 2
rank #8,290 # top 37%
last wipe 6d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5214:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040014:0023:0008:0017:0003: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 18 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 Sep6 Oct13 Oct21 Oct29 Oct

Top 37% 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 gap6.9 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Thu 22 OctThu 15 OctFri 9 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 21:12 UTC6d ago 1 NaN running 0
1 Thu 15 Oct, 23:39 UTC13d ago 1 halved by day 2 6.9 days 0
2 Fri 9 Oct, 20:07 UTC19d ago 1 halved by day 1 6.1 days 0
3 Thu 1 Oct, 21:06 UTC FW27d ago 0 NaN 8 days 0
4 Thu 24 Sep, 21:06 UTC34d ago 1 halved by day 2 7 days 0
5 Fri 18 Sep, 02:56 UTC41d ago 1 halved by day 2 6.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

3500 · seed 1330446348
Map of Terabit.io
map
Procedural Map
size
3500
seed
1330446348
Open on RustMaps

Server

srv.info()
address
207.174.41.154:28015
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 21:12 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 · 513 on average575/625
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average413/450
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average78/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average74/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average54/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 238 on average188/225

Quick answers

From the figures on this page.

Player counts

What position does Terabit.io take in the server rankings?

Rank #8,290 on seven-day player hours for Terabit.io, within the top 37% of all ranked servers.

How full does Terabit.io run?

The sample now reads 0 players for Terabit.io, out of 40 slots. Over the last seven days it averaged 0 players and peaked at 2. Peak hour in the last 48 hours: 14:00 UTC, mean 1 players.

About the server

How well does Terabit.io perform?

Averaged over 48 hours: 203 server fps, never under 170. Entity numbers reached 70,602, and that includes buildings, deployables and the rest. The memory field tops out at 3,310 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is Terabit.io on?

Rust network protocol 2635 and build 168909 on Linux is what Terabit.io runs. Steam updates your game for you, but the protocol must match to join.

How reliable is Terabit.io, and is it online now?

The current sample puts Terabit.io online. A restart about 6 days 14 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 158 of 168, 94%. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is Terabit.io hosted?

There is no region published for Terabit.io. Rust Data does not look up where the machine stands; it shows where a server says it is. 207.174.41.154:28015 is its address.

Settings and map

Which rules apply on Terabit.io, and what settings?

You will not find a gather rate in the string Terabit.io. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. VAC is running: Valve's anti-cheat is on.

Which map has Terabit.io loaded?

The game generates the map on Terabit.io: procedural, size 3,500, seed 1330446348. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does Terabit.io wipe, and on what schedule?

Irregular wipe times on Terabit.io leave no next wipe to forecast. 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 6 days 16 hours ago.

What is wipe day on Terabit.io like?

Recent wipes averaged 1 players at their peak. 15 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 2.

Tags and filters

Where does Terabit.io appear among Rust Data lists and filters?

The Rust Data lists that Terabit.io fits are: 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; Last wipe: In the last week.

Which meanings do the tags on Terabit.io hold?

Read by the game's server browser, the tags Terabit.io publishes are: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not 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.

Connecting

How can I connect to Terabit.io?

In Rust, F1 opens the console: type client.connect 207.174.41.154: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 mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players Slot count: 40.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not 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 74,292 players 11,842 servers online