Offline 108.52.202.42:28015 checked 5d ago
Philly Naval Update Server
Connect
srv = rust.server("108.52.202.42:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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, measured since 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
3500 · seed 592992545
- map
- Procedural Map
- size
- 3500
- seed
- 592992545
Server
srv.info()- address
- 108.52.202.42:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 22:19 UTC
- hostname
- –
- first seen
- 23 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 58/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 101/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 21/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 79/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 73/200 |
Quick answers
From the figures on this page.
Population data
How does Philly Naval Update Server compare in the rankings?
Player hours over seven days put Philly Naval Update Server at #15,270, in the top 69% of the ranked set.
How full does Philly Naval Update Server run?
The current row shows Philly Naval Update Server offline; the last response was 5 days 11 hours ago. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on Philly Naval Update Server?
Rust network protocol 2635 and build 169075 on Windows is what Philly Naval Update Server runs. Steam updates your game for you, but the protocol must match to join.
Is Philly Naval Update Server up, and what does its uptime show?
The latest sample has Philly Naval Update Server offline, with a last sighting 5 days 11 hours ago. 4 of 144 hours up over the last 6 full days, or 3%. Its earliest recorded date in Rust Data is 23 October 2026.
Which location does Philly Naval Update Server run from?
There is no region published for Philly Naval Update Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 108.52.202.42:28015.
Rules, settings, map
Which settings and rules does Philly Naval Update Server run?
You will not find a gather rate in the string Philly Naval Update Server. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Philly Naval Update Server selected?
The game generates the map on Philly Naval Update Server: procedural, size 3,500, seed 592992545. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does Philly Naval Update Server wipe, and on what schedule?
Too few wipes are on record for Philly Naval Update Server to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 6 days 9 hours ago, and that is the one in play.
Lists and tags
Which Rust Data filters and lists contain Philly Naval Update Server?
The Rust Data lists that Philly Naval Update Server fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Philly Naval Update Server?
Read by the game's server browser, the tags Philly Naval Update Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): 20 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs169075 (Build): The server runs build 169075; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Philly Naval Update Server?
In Rust, F1 opens the console: type client.connect 108.52.202.42:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.