Open every day, at every hour Admission free 11,672 servers and 34,284 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

This server publishes no banner

Exhibit no. 13,052Acc. 2026.13052

TestServ

Rust server · in the archive since 19 September 2026

Offline 5.68.240.132:28015 checked 10d ago

To visit
Players now 1/ 500
0% full
7-day average0peak –
Rank#13,052top 59%
Last wipe24d agoSun 4 Oct, 10:46 UTC · no schedule published
Next wipe–no rhythm it keeps

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectedlast seen, 18 Oct 2026, 10:05 UTCAll times UTC.

The record of each wipe

  1. Fri 9 Oct 202604:15 UTC19d ago
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    1
  2. Sun 4 Oct 202606:16 UTC24d ago
    Peak
    1
    Crowd
    held half
    Lasted
    4.9 days
    Players before
    0
  3. Sat 3 Oct 202621:52 UTC25d ago
    Peak
    1
    Crowd
    –
    Lasted
    0.4 days
    Players before
    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.

The rhythm

Wipe schedule

no rhythm it keeps

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

2.6 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
100%crowd heldof its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 9 OctSun 4 OctSat 3 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.

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Folder 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.

Folder 3

Rank

RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct11 Oct18 Oct25 Oct

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

Related exhibits

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags and filters

What do the server tags on TestServ mean?

You can see the tags TestServ publishes, read by the game's server browser: gmrust (Game mode): This server runs standard Rust survival; mp500 (Max players): Slot count: 500; ts8 (Group limit): The default cap of 8 per team applies here; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code field is empty. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.

Which Rust Server History lists and filters include TestServ?

The Rust Server History lists that feature TestServ are: Rust community servers. 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.

Server entry

Which version of Rust does TestServ run?

Rust network protocol 2634 and build 167781 is the build TestServ runs, on Windows. Steam updates your game for you; joining needs the same protocol.

Is TestServ online, and how reliable is it?

Offline now, TestServ was last seen 10 days 17 hours ago. Of 168 hours in the last 7 full days, 0 were up: 0% of the time. First seen by Rust Server History on 19 September 2026.

Where is TestServ located?

No region is published by TestServ. The location on Rust Server History is what a server says, not a lookup of where the machine stands. Its entry gives 5.68.240.132:28015 as the address.

Wipe log

What does wipe day look like on TestServ?

An average peak of 1 players was drawn by its recent wipes. 0 hours into the latest wipe the crowd peaked. Above half that peak until the next wipe it stayed in 100% of its recent wipes.

What is the wipe schedule on TestServ?

There is no next wipe to predict on TestServ, which wipes at irregular times. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. Made 24 days 16 hours ago, the current world is what it runs now.

Population

How does TestServ rank against other Rust servers?

Over seven days of player hours, TestServ ranks #13,052, inside the top 59% of all ranked servers.

How busy is TestServ?

No current count exists for TestServ; it was last seen 10 days 17 hours ago.

Map and rules

What are the rules and settings on TestServ?

You will not find a gather rate in the name of TestServ. The limit of 8 players per group is the game's default. Recorded as survival, with this note: the usual game, with gathering, building and raiding. PvP and raiding are enabled. The Community section of the server browser carries it. The anti-cheat VAC from Valve is active.

Which map does TestServ run?

The game generates the map on TestServ, which is procedural.

How to join

How do I join TestServ?

Enter client.connect 5.68.240.132:28015 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you.

The label explained

Server tags

What each tag this server publishes means.

Published as mp500,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode This server runs standard Rust survival.
mp500
Max players Slot count: 500.
ts8
Group limit The default cap of 8 per team applies here.
v2634
Protocol To join, your game has to be on protocol 2634.
cs167781
Build Build number: 167781.
ptrak
Networking Networking runs on RakNet, the game's standard layer.
$r?
Region code The region code 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.