This server publishes no banner
Exhibit no. 8,939Acc. 2026.8939
TEST COPY (update check)
Rust server · in the archive since 23 October 2026
Offline 42.114.93.106:28025 checked 5d ago
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.
The record of each wipe
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.
The rhythm
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Players
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 40% 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 TEST COPY (update check) mean?
You can see the tags TEST COPY (update check) publishes, read by the game's server browser: gmrust (Game mode): This server runs standard Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Teams are capped at 8, the default the game ships; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code field is empty; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; ^y (Carbon): Carbon is the plugin framework in use. 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 TEST COPY (update check)?
The Rust Server History lists that feature TEST COPY (update check) are: Modded Rust servers: the record. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server entry
Which version of Rust does TEST COPY (update check) run?
On Windows, TEST COPY (update check) runs Rust network protocol 2635 and build 168909. Joining requires your game to be on the same protocol; Steam keeps it updated for you.
Is TEST COPY (update check) online, and how reliable is it?
The record shows TEST COPY (update check) offline at this moment, last seen 5 days 12 hours ago. 6 of 120 hours, or 5% of the time, over the last 5 full days. The first sighting by Rust Server History was on 23 October 2026.
Where is TEST COPY (update check) located?
You will find no region published by TEST COPY (update check). The location on Rust Server History is what a server says, not a lookup of where the machine stands. You will find it at 42.114.93.106:28025.
Wipe history
What is the wipe schedule on TEST COPY (update check)?
Its rhythm is not yet clear: too few of TEST COPY (update check)'s wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. 10 days 2 hours ago its current world was made.
Player record
How does TEST COPY (update check) rank against other Rust servers?
Over seven days of player hours, TEST COPY (update check) ranks #8,939, inside the top 40% of all ranked servers.
How busy is TEST COPY (update check)?
No current count exists for TEST COPY (update check); it was last seen 5 days 12 hours ago. Stored history gives a seven-day average of 0 players and a peak of 1.
Rules and settings
What are the rules and settings on TEST COPY (update check)?
The name of TEST COPY (update check) carries no gather rate. The limit of 8 players per group is the game's default. Under game mode, the entry reads survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are permitted. Plugins or settings alter the game here, and the browser lists the server under Modded. Plugins in use: Carbon. The anti-cheat VAC from Valve is active.
Which map does TEST COPY (update check) run?
A procedural map is what TEST COPY (update check) runs; the game generates it.
Join record
How do I join TEST COPY (update check)?
Entering client.connect 42.114.93.106:28025 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf.
The label explained
Server tags
What each tag this server publishes means.
Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
mp10
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^z
^y
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.