# Amsterdam, Netherlands → Hong Kong RTT

🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇭🇰 **Hong Kong (HKG)**

Measurement round: `2026-08-16T04:07:28Z`.

For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Amsterdam to Hong Kong averaged 155.9 ms, with a minimum of 149.39 ms and a maximum of 177.73 ms. All 50 probes were answered, so the zero packet loss and 4.48 ms jitter describe a stable sample rather than a lossy path.

The great-circle distance of 9,297.6 km gives a vacuum light-time floor of 62.03 ms and a realistic fiber floor of 91.05 ms. The observed average is 1.71 times that fiber floor, which translates to a fiber efficiency of 58.4%; the extra time over the floor is the route's real-world distance penalty.

This route ranks 12th among the 19 outbound routes measured from Amsterdam in this round. Its standard deviation of 5.82 ms is about 3.7% of the average, slightly above the 3.28% median variability for the 19-route set, so the path is consistent but a touch more variable than the midpoint of the group.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **155.9 ms**                                               |
| Jitter               | **4.48 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **91.05 ms**                                               |
| Fiber Efficiency     | **58.4%**                                                  |
| Latency Tier         | Fair                                                       |
| Source Region        | [Europe](/docs/network/latency/regions/europe)             |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |

## Ping Measurement Series

The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart.

## Download This Route's Data

This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,297.6 km** |
| Vacuum RTT floor                              | **62.03 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **91.05 ms**   |
| Low-latency fiber material floor              | **90.68 ms**   |
| Engineering floor (5% path allowance)         | **95.61 ms**   |
| Research 1.33× mapped-fiber reference         | **121.1 ms**   |
| Estimated unamplified path loss               | **1952.5 dB**  |
| Transparent optical spans / inline amplifiers | **123 / 122**  |
| Published RTT inflation over fiber floor      | **1.71×**      |

Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency).

## Stability & Trend

The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

| Round Statistic    | Value         |
| ------------------ | ------------- |
| Minimum RTT        | **149.39 ms** |
| Average RTT        | **155.9 ms**  |
| Maximum RTT        | **177.73 ms** |
| Standard deviation | **5.82 ms**   |
| Stdev / average    | **3.7%**      |

## Route Context

* Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Hong Kong to Amsterdam latency and RTT](/docs/network/latency/pairs/hkg-ams-rtt) — 154.4 ms

**Fastest routes departing Amsterdam (AMS)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms
* [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms
* [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms
* [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms

**Fastest routes arriving at Hong Kong (HKG)**

* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms
* [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms
* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms

**Same corridor (Europe → Asia Pacific)**

* [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms
* [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms
* [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms

## About This Measurement

Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA.

The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0".

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-hkg-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.