Facepunch Playtest
Online 79.137.98.20:28015 checked 8m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 56% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 17:40 UTC FW28d ago | 0 | – | running | 0 |
| Mon 28 Sep, 07:20 UTC31d ago | 28+1 queue | halved by day 1 | 3.4 days | 0 |
| Thu 24 Sep, 10:57 UTC35d ago | 0 | – | 3.8 days | 0 |
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| Server | Profile | Players now |
|---|---|---|
| Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 486 on average | 46 / 250 |
| Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 321 on average | 78 / 200 |
| Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 283 on average | 256 / 300 |
| Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 279 on average | 11 / 100 |
| Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 313 / 375 |
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 256 on average | 267 / 300 |
Quick answers
from the figures on this pageWipe cycle
On what cycle does Facepunch Playtest wipe?
The next wipe on Facepunch Playtest cannot be predicted, because it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 28 days 9 hours ago the current world was made.
Wipe day on Facepunch Playtest: what should you expect?
The average busiest count over recent wipes is 9 players. Peak population for the latest wipe came 0 hours after it began. Above half that peak until the next wipe held in 0% of recent wipes. The fall below half arrived by day 1 when it didn't hold.
Server
What is the hosting location of Facepunch Playtest?
No region is published by Facepunch Playtest. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 79.137.98.20:28015 is its address.
Which Rust version is Facepunch Playtest on?
On Windows, Facepunch Playtest runs Rust network protocol 2635 and build 169375. The protocol has to match before you can join; Steam updates it automatically.
What uptime does Facepunch Playtest show, and is it up?
As of the latest refresh, Facepunch Playtest is online. About 2 days 7 hours ago is when it last restarted, judged by its reported uptime. Of 168 hours in the last 7 full days, 167 were up: 99%. It entered Rust Server Analytics records on 13 September 2026.
What performance does Facepunch Playtest show?
Server fps averaged 56 over the last 48 hours, with a floor of 32. Entity count reached 402,000, covering buildings, deployables and the rest of the world. Peak memory was 11,693 MB. A climbing entity count and low fps are the lag players perceive.
Tags
How should the tags on Facepunch Playtest be read?
Tags from Facepunch Playtest, as read by the game's server browser, are: official (official): Run by Facepunch or one of its partners: the servers in Rust's Official tab. Rust does not publish this, so it is kept by hand; gmrust (Game mode): Survival in the standard Rust format; mp0 (Max players): 0 slots in total; ts100 (Group limit): The cap is 100 players per team; v2635 (Protocol): To join, your game version must match protocol 2635; cs169375 (Build): The game build is 169375; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does Facepunch Playtest appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include Facepunch Playtest: Official Rust servers. On the server list, the filters that return it are: Type: No plugins at all; Group limit: 5 or more; Boxes: Official only.
By whom is Facepunch Playtest run?
A playrust.com hostname is published by Facepunch Playtest, as by 124 other servers we track, so one operator most likely runs them all.
Population
Where does Facepunch Playtest sit among Rust servers?
Player hours for the last seven days place Facepunch Playtest at #12,392, in the top 56% of the ranked field.
At what level does Facepunch Playtest run its population?
Facepunch Playtest currently records 0 players. Seven-day figures: an average of 0 players and a peak of 1. Across the last 48 hours, 13:00 UTC shows the highest average: 1 players.
Map and rules
What are the settings on Facepunch Playtest, and its rules?
No gather rate is given in the name of Facepunch Playtest. Players per group: up to 100. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. Rust's official server tab includes it. Anti-cheat status: VAC on.
What is the map for Facepunch Playtest?
Facepunch Playtest uses a procedural map of size 4,500 with seed 1377699477, generated by the game. Size and seed fix the map, so a RustMaps view is available from this page.
Connection
What is the way onto Facepunch Playtest?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 79.137.98.20:28015.