# Hong Kong → Berlin, Germany RTT

🇭🇰 **Hong Kong (HKG)** → 🇩🇪 **Berlin, Germany (BER)**

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

In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Hong Kong to Berlin, Germany averaged 145.1 ms, with a minimum of 138.49 ms and a maximum of 164.88 ms; all 50 probes succeeded, packet loss was 0%, and jitter was 5.8 ms.

The 8,767.1 km great-circle distance puts the fiber floor at 85.85 ms, so the measured average is 1.69 times the floor and fiber efficiency reaches 59.2%.

Ranked 9th among the 19 outbound routes in this round, this route sits on the faster side of the field. Its standard deviation of 6.67 ms is 4.60% of the average, higher than the network's median spread-to-average ratio of 3.28%, so the tail toward 164.88 ms adds noticeable spread despite the good mean RTT.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **145.1 ms**                                               |
| Jitter               | **5.8 ms**                                                 |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **85.85 ms**                                               |
| Fiber Efficiency     | **59.2%**                                                  |
| Latency Tier         | Good                                                       |
| 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 [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **8,767.1 km** |
| Vacuum RTT floor                              | **58.49 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **85.85 ms**   |
| Low-latency fiber material floor              | **85.51 ms**   |
| Engineering floor (5% path allowance)         | **90.16 ms**   |
| Research 1.33× mapped-fiber reference         | **114.19 ms**  |
| Estimated unamplified path loss               | **1841.1 dB**  |
| Transparent optical spans / inline amplifiers | **116 / 115**  |
| Published RTT inflation over fiber floor      | **1.69×**      |

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        | **138.49 ms** |
| Average RTT        | **145.1 ms**  |
| Maximum RTT        | **164.88 ms** |
| Standard deviation | **6.67 ms**   |
| Stdev / average    | **4.6%**      |

## Route Context

* Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* 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**

* [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 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 Berlin (BER)**

* [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms
* [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms
* [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms
* [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms
* [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 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
* [Singapore to Moscow latency and RTT](/docs/network/latency/pairs/sin-mow-rtt) — 147.7 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-ber.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 → Berlin 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-ber-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.