TEST COPY (update check)
Offline 42.114.93.106:28025 checked 5d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 40% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What is the wipe schedule on TEST COPY (update check)?
Its rhythm cannot yet be told: too few of TEST COPY (update check)'s wipes are on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 10 days 8 hours ago.
Player counts
How busy is TEST COPY (update check)?
The last time TEST COPY (update check) was seen was 5 days 19 hours ago, and it is offline now. A seven-day average of 0 players, with a peak of 1.
How does TEST COPY (update check) rank against other Rust servers?
The top 40% of ranked servers includes TEST COPY (update check), at #8,984 for player hours over the last seven days.
Map and rules
Which map does TEST COPY (update check) run?
A procedural map, generated by the game, runs on TEST COPY (update check).
What are the rules and settings on TEST COPY (update check)?
No gather rate appears in the name TEST COPY (update check). 8 players is the default group size, and that is the limit here. The server runs survival, standard play: gathering, building and raiding. You can fight other players and raid their bases. In the server browser it is Modded, meaning plugins or settings modify the game. Carbon plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does TEST COPY (update check) run?
Rust network protocol 2635 and build 168909 on Windows is what TEST COPY (update check) runs. Steam updates your game for you, and the protocol has to match for you to join.
Is TEST COPY (update check) online, and how reliable is it?
Last seen 5 days 19 hours ago, TEST COPY (update check) is offline right now. 6 of 144 hours up over the last 6 full days, which is 4%. The first record of it on Rust Heatmap is 23 October 2026.
Where is TEST COPY (update check) located?
Nothing about a region comes from TEST COPY (update check). What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 42.114.93.106:28025.
Lists and filters
Which Rust Heatmap lists and filters include TEST COPY (update check)?
The Rust Heatmap lists that TEST COPY (update check) fits are: Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks brings it up.
What do the server tags on TEST COPY (update check) mean?
gmrust (Game mode): Rust survival, standard rules; mp10 (Max players): Slot count: 10; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): This build is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; ^y (Carbon): Plugins run through Carbon are the tags TEST COPY (update check) publishes, and the server browser reads them. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
Connect
How do I join TEST COPY (update check)?
To join by console, open it with F1 in Rust and enter client.connect 42.114.93.106:28025. Or press Launch Rust on this page, which connects you through Steam.