r2020-test
Offline 208.88.69.27:38253 checked 8d ago
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
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 316/ 300
- 591/ 600
- 452/ 500
- 128/ 200
- 565/ 525
- 213/ 250
Quick answers
Tags and listings
Where does r2020-test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry r2020-test are: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on r2020-test?
The server browser shows these tags for r2020-test: gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): It holds 1 players; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167398 (Build): This server runs build 167398; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
Where can you find r2020-test?
There is no published region for r2020-test. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 208.88.69.27:38253.
Is r2020-test up, and how often does it stay online?
r2020-test is down at the moment; it was last up 8 days 17 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 9 October 2026.
What Rust version is r2020-test on?
Rust network protocol 2634 and build 167398 is what r2020-test runs, on Linux. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
When does r2020-test wipe?
The wipes recorded for r2020-test are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 8 days 17 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is r2020-test running?
The name of r2020-test contains no gather rate. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. The server browser lists it under Community, making it a community server. The server runs Valve's anti-cheat, VAC.
Population
How many players are on r2020-test?
r2020-test was last seen 8 days 17 hours ago and is offline as you read this.
What's r2020-test's rank among Rust servers?
Over the last seven days, r2020-test is #15,869 by player hours, among the top 72% of all ranked servers.
Getting in
What's the process to join r2020-test?
Open Rust and press F1, then type client.connect 208.88.69.27:38253. Alternatively, click Launch Rust on this page to join via Steam.