Broker Server Directory / Blauwal Securities FZCO / BlauwalSecurities-Trade
BlauwalSecurities-Trade is a MT5 trading server operated by Blauwal Securities FZCO, with 44 verified access points across China, Hong Kong, Japan. Found via direct network lookup, not estimated. Exact IP addresses and ports are available as a paid CSV download below; hosting providers are listed publicly.
BlauwalSecurities-Trade's access points run on infrastructure from the following providers, based on public network (IP allocation) registration data:
| IP Address | Port | City | Region | Country | Coordinates | Network / ISP |
|---|---|---|---|---|---|---|
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hangzhou | Zhejiang | CN | 30.2943, 120.1663 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Shenzhen | Guangdong | CN | 22.5455, 114.0683 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Beijing | Beijing | CN | 39.9110, 116.3950 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Chengdu | Sichuan | CN | 30.6667, 104.0667 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hong Kong | Central and Western | HK | 22.3964, 114.1090 | 🔒 Locked |
| 🔒 Locked | 🔒 | Hong Kong | Central and Western | HK | 22.3964, 114.1090 | 🔒 Locked |
| 🔒 Locked | 🔒 | Tokyo | Tokyo | JP | 35.6895, 139.6920 | 🔒 Locked |
| 🔒 Locked | 🔒 | Tokyo | Tokyo | JP | 35.6895, 139.6920 | 🔒 Locked |
Exact IP addresses and ports are locked. Unlock the full connection data (every IP address and port, mapped per access point) for this server as a downloadable CSV for a one-time fee.
Blauwal Securities FZCO operates 1 known MT4/MT5 server in this directory.
The physical distance between your trading application and your broker's MT4/MT5 server directly affects order round-trip time. Traders and platform developers increasingly colocate their own infrastructure near their broker's real servers rather than routing every request over a long-haul connection from home.
BlauwalSecurities-Trade is a MT5 trading server operated by Blauwal Securities FZCO, with 44 verified access points across China, Hong Kong, Japan.
The exact IP addresses and ports for BlauwalSecurities-Trade's 44 access points are available as a downloadable CSV for a one-time fee (see the unlock section on this page). Publicly, we've verified this server has infrastructure in: China, Hong Kong, Japan.
BlauwalSecurities-Trade's access points run on infrastructure from: Hangzhou Alibaba Advertising Co (30), Hangzhou Alibaba Advertising Co., Ltd. (9), Amazon.com, Inc. (3), Aliyun Computing Co (1), Amazon Technologies Inc (1). This is based on public network (IP allocation) registration data, not a statement from Blauwal Securities FZCO itself.
Symbol data for BlauwalSecurities-Trade hasn't been captured yet. We gather this organically from real customer trading activity through MetaTraderAPI (not from broker credentials of our own, which we don't have) -- check back as more accounts connect.
Leverage data for BlauwalSecurities-Trade hasn't been observed yet. Like our symbol data, this is gathered organically from real customer accounts connecting through MetaTraderAPI -- check back as more accounts connect.
China, Hong Kong, Japan.
No. This is an independent, third-party directory of publicly discoverable MT4/MT5 server infrastructure, compiled by MetaTraderAPI. It is not affiliated with, endorsed by, or operated by Blauwal Securities FZCO.
MetaTraderAPI gives you one metered REST + WebSocket gateway across every MT4/MT5 broker — connection handling, reconnection, and usage metering built in.
Get API access