Online 95.65.49.211:28016 checked 10m ago
[Vanilla/MAX4] GrandCity | NooBServeR | Classic ++
Connect
srv = rust.server("95.65.49.211:28015")
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 17 Sep. 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 best
Top 27% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 8d 18h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 18h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 15d 18h | Thu 12 Nov, 18:33 UTC | wipe |
| 2 | 36d 18h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 43d 18h | Thu 10 Dec, 18:33 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 40 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 18:33 UTC12d ago | 2 | NaN | running | 0 |
| 1 | Thu 1 Oct, 18:08 UTC FW26d ago | 2 | halved by day 5 | 14 days | 0 |
| 2 | Thu 17 Sep, 18:16 UTC40d ago | 3 | halved by day 3 | 14 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.
display(srv.map, srv.info())
Map
4500 · seed 725511
- map
- Procedural Map
- size
- 4500
- seed
- 725511
Server
srv.info()- address
- 95.65.49.211:28016
- region
- –
- max players
- 150
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 15 Oct 2026, 19:17 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 1 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 67/225 |
| 2 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 13/200 |
| 3 | [NA] Willjum's Solo Only | Thursday Wipes | NA · groups of 8+ · weekly · 26 on average | 11/100 |
| 4 | [EU] Willjum's Solo Only | Thursday Wipes | EU · groups of 8+ · weekly · 25 on average | 11/175 |
| 5 | QS『芬达』100000倍/10.27/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 23 on average | 11/100 |
Quick answers
From the figures on this page.
Population data
What position does [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ take in the server rankings?
Over the last seven days [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ sits at #5,961 on player hours, in the top 27% of ranked servers.
How full does [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ run?
Current row: 0 players on [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++, against 150 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 15:00 UTC is the busiest, at 1 players.
Server facts
How smoothly does [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ run?
The 48-hour average is 120 server fps, with a low of 96. Entity numbers reached 120,324, and that includes buildings, deployables and the rest. The memory field tops out at 5,371 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++, and is it online now?
[Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ reports itself online at the current refresh. Count back 14 hours from its reported uptime to get the last restart. Uptime of 85% across the last 7 full days: 142 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ run from?
No region is published by [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 95.65.49.211:28016.
Map and rules
Which settings and rules does [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ run?
You will not find a gather rate in the string [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ selected?
Size 4,500, seed 725511: the procedural map on [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ wipe, and on what schedule?
The wipe rhythm for [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ is every 4 weeks on Thursday at 18:33 UTC. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 12 days 4 hours ago. The tags list wipes as weekly.
What is wipe day on [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ like?
Recent wipes averaged 2 players at their peak. 40 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 4.
Lists and tags
Which lists on Rust Data hold [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++, and which filters?
On Rust Data, [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ appears in these lists: Modded Rust servers and Rust servers for beginners. It appears under these filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.
How should you read the server tags on [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++?
Read by the game's server browser, the tags [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++ publishes are: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): Slot count: 150; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^w (Weekly): Wipes run weekly; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join [Vanilla/MAX4] GrandCity | NooBServeR | Classic ++?
Enter client.connect 95.65.49.211:28016 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/ej6VTh8e4f is the website recorded for it.