Terabit.io
Online 207.174.41.154:28015 checked 8m ago
Server instruments
last reading Thu 08:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 170 · below 20 is lag, below 10 is badEntities
48 h range 68,158–70,602 · memory 2,918 MBUptime
6 days 10 hours since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 37% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 15 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 21:12 UTC6d ago | 1 | – | running | 0 |
| Thu 15 Oct, 23:39 UTC13d ago | 1 | halved by day 2 | 6.9 days | 0 |
| Fri 9 Oct, 20:07 UTC19d ago | 1 | halved by day 1 | 6.1 days | 0 |
| Thu 1 Oct, 21:06 UTC FW27d ago | 0 | – | 8 days | 0 |
| Thu 24 Sep, 21:06 UTC34d ago | 1 | halved by day 2 | 7 days | 0 |
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 393/400
- 346/350
- 38/250
- 32/250
- 47/100
- 151/200
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Terabit.io?
An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 15 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 2 it fell below half.
What wipe timing does Terabit.io follow?
There is no next wipe to predict: Terabit.io wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 6 days 13 hours ago.
Tags
How should you read the tags on Terabit.io?
These are the tags Terabit.io publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Terabit.io appear in Rust Metrics lists and filters?
On Rust Metrics, Terabit.io sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Population
Where does Terabit.io sit in the rankings?
Player hours over seven days put Terabit.io at #8,304, in the top 37% of all ranked servers.
What player count does Terabit.io carry?
0 of 40 slots are filled on Terabit.io right now. Check: players over seven days. Average 0, peak 2. The last 48 hours peaked at 14:00 UTC, averaging 1 players at that hour.
Server
What location is Terabit.io hosted in?
Reading: location. Terabit.io gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 207.174.41.154:28015.
What Rust version is Terabit.io on?
Rust network protocol 2635 and build 168909 on Linux is the build Terabit.io runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for Terabit.io?
Over the last 48 hours the average was 203 server fps; the floor was 170. Reading: 70,602 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 3,310 MB. Lag, as players feel it, is low fps plus a climbing entity count.
Is Terabit.io up, and how often does it stay up?
Check: connection. Terabit.io is online at this moment. Reading: uptime. About 6 days 10 hours ago it restarted, on its own count. Reading: 94% uptime over the last 7 full days. It was up 158 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Settings and map
What rules does Terabit.io enforce, and what are its settings?
Check: gather rate. The name Terabit.io does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is Terabit.io on?
Size 3,500 and seed 1330446348: the game generates the procedural map on Terabit.io from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
How to join
How can you get onto Terabit.io?
Check: join. Open Rust, press F1, then enter client.connect 207.174.41.154:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.