Hong Kong → Berlin, Germany RTT
ICMP echo RTT measurements from Hong Kong, Hong Kong to Berlin, Germany: average, minimum, maximum, jitter, packet loss, and fiber efficiency.
🇭🇰 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 |
| Destination Region | 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.
Ping series: HKG → BER
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 145.1 ± 0.94 ms (SE)
Sample distribution: box = interquartile range (140.7–146.6 ms), median 142.8 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (85.8 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 138.49 |
| 2 | 100 | 144.25 |
| 3 | 200 | 147.47 |
| 4 | 300 | 141.92 |
| 5 | 400 | 143.79 |
| 6 | 500 | 142.67 |
| 7 | 600 | 152.70 |
| 8 | 700 | 143.39 |
| 9 | 800 | 160.72 |
| 10 | 900 | 147.61 |
| 11 | 1000 | 158.24 |
| 12 | 1100 | 146.26 |
| 13 | 1200 | 141.84 |
| 14 | 1300 | 139.84 |
| 15 | 1400 | 140.80 |
| 16 | 1500 | 138.74 |
| 17 | 1600 | 164.88 |
| 18 | 1700 | 149.58 |
| 19 | 1800 | 142.44 |
| 20 | 1900 | 139.99 |
| 21 | 2000 | 139.74 |
| 22 | 2100 | 141.85 |
| 23 | 2200 | 145.05 |
| 24 | 2300 | 149.56 |
| 25 | 2400 | 144.57 |
| 26 | 2500 | 143.15 |
| 27 | 2600 | 142.88 |
| 28 | 2700 | 139.23 |
| 29 | 2800 | 141.87 |
| 30 | 2900 | 141.20 |
| 31 | 3000 | 140.01 |
| 32 | 3100 | 141.00 |
| 33 | 3200 | 142.59 |
| 34 | 3300 | 140.61 |
| 35 | 3400 | 144.39 |
| 36 | 3500 | 139.67 |
| 37 | 3600 | 146.75 |
| 38 | 3700 | 160.83 |
| 39 | 3800 | 145.34 |
| 40 | 3900 | 142.47 |
| 41 | 4000 | 144.58 |
| 42 | 4100 | 140.32 |
| 43 | 4200 | 147.07 |
| 44 | 4300 | 141.23 |
| 45 | 4400 | 143.77 |
| 46 | 4500 | 139.42 |
| 47 | 4600 | 139.70 |
| 48 | 4700 | 139.02 |
| 49 | 4800 | 163.40 |
| 50 | 4900 | 158.11 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Hong Kong (22.27832, 114.17469) and Berlin (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 () | 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.
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% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 145.0 ms
- Minimum
- 143.5 ms
- Maximum
- 146.6 ms
- Average loss
- 0.03%
Route Context
- Departure PoP: Hong Kong (HKG)
- Destination PoP: Berlin (BER)
- Region overview: Asia Pacific → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Berlin to Hong Kong latency and RTT — 144.9 ms
Fastest routes departing Hong Kong (HKG)
- Hong Kong to Taipei latency and RTT — 14.7 ms
- Hong Kong to Singapore latency and RTT — 31.5 ms
- Hong Kong to Tokyo latency and RTT — 44.9 ms
- Hong Kong to Moscow latency and RTT — 118.2 ms
- Hong Kong to Seattle latency and RTT — 131.6 ms
Fastest routes arriving at Berlin (BER)
- Frankfurt to Berlin latency and RTT — 6.1 ms
- Amsterdam to Berlin latency and RTT — 7.2 ms
- Paris to Berlin latency and RTT — 15.5 ms
- London to Berlin latency and RTT — 16.2 ms
- Marseille to Berlin latency and RTT — 20.6 ms
Same corridor (Asia Pacific → Europe)
- Taipei to Moscow latency and RTT — 132.7 ms
- Singapore to Marseille latency and RTT — 140.6 ms
- Singapore to Moscow latency and 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. 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 or browse more city-pair routes.