# Hong Kong → Frankfurt, Germany RTT

🇭🇰 **Hong Kong (HKG)** → 🇩🇪 **Frankfurt, Germany (FRA)**

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

In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes sent 100 ms apart from Hong Kong to Frankfurt returned with zero packet loss, giving an average round-trip time of 150.7 ms, a minimum of 147.02 ms, and a maximum of 163.83 ms. The standard deviation was 3.53 ms and jitter was 2.66 ms, so the path stayed fairly steady across the sample.

The 9,177.1 km great-circle distance sets a round-trip vacuum floor of 61.22 ms and a fiber floor of 89.87 ms. The 150.7 ms average is 1.68 times that fiber floor, which corresponds to 59.6 percent fiber efficiency and a 60.83 ms difference from the straight-line fiber minimum.

Within the same round, this route ranked 10th among 19 outbound paths measured from Hong Kong. The median standard-deviation-to-average ratio for those paths was 3.28 percent; this route's ratio was about 2.34 percent, indicating latency variation below the typical level for the set.

## Latency Summary

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

## 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 [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,177.1 km** |
| Vacuum RTT floor                              | **61.22 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **89.87 ms**   |
| Low-latency fiber material floor              | **89.51 ms**   |
| Engineering floor (5% path allowance)         | **94.37 ms**   |
| Research 1.33× mapped-fiber reference         | **119.53 ms**  |
| Estimated unamplified path loss               | **1927.2 dB**  |
| Transparent optical spans / inline amplifiers | **121 / 120**  |
| Published RTT inflation over fiber floor      | **1.68×**      |

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        | **147.02 ms** |
| Average RTT        | **150.7 ms**  |
| Maximum RTT        | **163.83 ms** |
| Standard deviation | **3.53 ms**   |
| Stdev / average    | **2.3%**      |

## Route Context

* Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe)
* 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**

* [Frankfurt to Hong Kong latency and RTT](/docs/network/latency/pairs/fra-hkg-rtt) — 152 ms

**Fastest routes departing Hong Kong (HKG)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms
* [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms
* [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms
* [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms

**Fastest routes arriving at Frankfurt (FRA)**

* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms
* [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms
* [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms
* [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms
* [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms

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

* [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms
* [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms
* [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 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/hkg-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Frankfurt 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/hkg-fra-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.