RUST METRICSFlight deck · live data
Data live Servers11,596 Players34,117 Populated2,818 Fresh wipes 3 h66 Scan5 min
‹ All servers75.178.1.232:28015
Offline Full Queue Fresh wipe Wipe due No query

RedsTestServer

Offline 75.178.1.232:28015 checked 7d ago

COM 1 · connect

Server instruments

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

Players now

10% 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#13,093top 59%
Last wipe9d agono schedule published
Next wipe–no wipe 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
15k10k15k20k18 Oct20 Oct22 Oct23 Oct25 Oct27 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

Wipe schedule

When does RedsTestServer wipe?

Its rhythm cannot be told from the wipes of RedsTestServer 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. The world it runs now was made 9 days 7 hours ago.

Tag meanings

How should you read the tags on RedsTestServer?

Tags published by RedsTestServer, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show RedsTestServer?

Rust Metrics lists featuring RedsTestServer: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does RedsTestServer sit in the rankings?

Ranking for RedsTestServer: #13,093 on seven-day player hours, top 59% of all ranked servers.

What player count does RedsTestServer carry?

Status for RedsTestServer: offline. Last seen 7 days 5 hours ago.

Server details

Which location does RedsTestServer run from?

Reading: location. RedsTestServer gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 75.178.1.232:28015.

What Rust version is RedsTestServer on?

Reading: RedsTestServer, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is RedsTestServer up, and how often does it stay up?

Check: connection. RedsTestServer is offline at this moment. Last contact was 7 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 18 October 2026, recorded by Rust Metrics.

Rules and settings

How is RedsTestServer configured, and what rules are in force?

Check: gather rate. The name RedsTestServer does not state one. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is RedsTestServer on?

The game generates a procedural map for RedsTestServer.

Connection

How do you connect to RedsTestServer?

To join: start Rust, press F1 and type client.connect 75.178.1.232: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,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.