Teste local x64
Offline 45.187.111.134:28185 checked 23d ago
No wipe seen yet, so its progress can't be tracked.
Players, performance and rank
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 71% 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
every wipe as a delivery, newest first- 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.
- Frontier - EU 10x | No BPs | Kits | Shop 0 / 16
- Atlas - EU 10x | No BPs | Kits | Shop 146 / 250
- TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPE 331 / 350
- Atlas - US 10x | No BPs | Kits | Shop 245 / 300
- KRAKEN | X10 | EU | KITS | RP | FPS+ 42 / 400
- HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] 41 / 150
Quick answers
From the figures on this page.
Player activity
What is the ranking of Teste local x64 against other Rust servers?
In the top 71% of all ranked servers sits Teste local x64, at #15,984 on hours played over seven days.
What is the current population on Teste local x64?
At the moment Teste local x64 is offline, having last been seen 23 days 21 hours ago.
Rules and settings
What are the rules on Teste local x64, and what settings does it run?
You get 64x gather on Teste local x64, going by its name. No group limit is published. It runs survival, gather, build and raid, as the standard game goes. You can raid and fight other players. The server browser files it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.
About the server
In which region is Teste local x64 based?
No region is published by Teste local x64. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 45.187.111.134:28185.
What is the uptime of Teste local x64, and is it online?
Teste local x64 is offline at the moment, with the last sighting 23 days 21 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 4 October 2026.
On what Rust version does Teste local x64 operate?
On Windows, Teste local x64 runs Rust network protocol 1069. Steam keeps your game updated; it has to be on the same protocol to join.
Map resets
How often does Teste local x64 wipe, and at what times?
There are too few of Teste local x64's wipes on record so far to show its rhythm. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month.
Server tags
Where does Teste local x64 appear in Rust Wipe Tracker lists and filters?
These Rust Wipe Tracker lists take Teste local x64: Rust servers above 10x gather and Rust community servers, unmodded. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Gather rate: More than 10x.
How should you read the tags on Teste local x64?
The game's server browser picks up these Teste local x64 tags: mp1 (Max players): It holds 1 slots; v1069 (Protocol): Join only if your game runs protocol 1069; rust (Custom tag): This isn't a standard Rust tag; it comes from the owner or a plugin. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.
How to join
What is the process to join Teste local x64?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 45.187.111.134:28185.