RUST METRICSFlight deck · live data
Data live Servers11,686 Players55,597 Populated3,415 Fresh wipes 3 h92 Scan5 min
‹ All servers31.134.74.69:28015
Offline Full Queue Fresh wipe Wipe due No query

Best Teammate Test

Offline 31.134.74.69:28015 checked 17d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,370top 65%
Last wipe17d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k30 Sep3 Oct6 Oct11 Oct14 Oct17 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 12:13 UTC17d ago 1 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on Best Teammate Test when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Best Teammate Test follow?

Its rhythm cannot be told from the wipes of Best Teammate Test on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 17 days 21 hours ago the current world was made.

Tag meanings

Which tags does Best Teammate Test carry, and what do they mean?

These are the tags Best Teammate Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Game build reading: 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Best Teammate Test?

On Rust Metrics, Best Teammate Test 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.

Population

Where does Best Teammate Test sit in the rankings?

Player hours over seven days put Best Teammate Test at #14,370, in the top 65% of all ranked servers.

How full does Best Teammate Test get?

Best Teammate Test is not responding; status offline, last seen 17 days 20 hours ago.

Server details

What location is Best Teammate Test hosted in?

No region comes from Best Teammate Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 31.134.74.69:28015.

What Rust version is Best Teammate Test on?

Reading: Best Teammate Test, Rust network protocol 2634 and build 167398, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Best Teammate Test, and is it online?

Reading: offline. Best Teammate Test last answered 17 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 30 September 2026.

Map and rules

What settings and rules apply on Best Teammate Test?

Reading the name gives no gather rate for Best Teammate Test. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is Best Teammate Test on?

The game generates a procedural map for Best Teammate Test.

Connection

How do you connect to Best Teammate Test?

To join: start Rust, press F1 and type client.connect 31.134.74.69:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Game build reading: 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.