ICMP round-trip time from Amsterdam, Netherlands, to Hong Kong: 50 samples, 152.8 ms average, 0% loss, and route latency context.

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

Measurement round: 2026-08-15T04:03:13Z.

During the 2026-08-15T04:03:13Z round, ICMP echo RTT from Amsterdam to Hong Kong averaged 152.8 ms across 50 samples at 100 ms intervals, with a minimum of 146.03 ms, a maximum of 181.51 ms, and a standard deviation of 6.24 ms. Zero packets were lost, and the route falls in the fair latency tier.

This route ranked 12th among the 19 outbound routes measured from Amsterdam in the same round, so it sits around the middle of the set. Its variability-to-average ratio of about 4.1% is above the 3.08% median across those routes, meaning the reply times fluctuated a bit more than the typical Amsterdam outbound path.

Relative to a straight-line fiber floor of 91.05 ms, the observed average is 1.68 times higher, equivalent to a fiber efficiency of 59.6%. The 35.48 ms range between slowest and fastest replies and 5.24 ms jitter show the route can vary noticeably, so latency-sensitive planners should treat the average as a baseline rather than a guarantee; ICMP RTT should not be used to predict end-user application performance.

Latency Summary

Metric	Value
RTT	152.8 ms
Jitter	5.24 ms
Packet Loss	0%
Standard Fiber Floor	91.05 ms
Fiber Efficiency	59.6%
Latency Tier	Fair
Source Region	Europe
Destination Region	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.

Ping series: AMS → HKG

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 152.8 ± 0.88 ms (SE)

Sample distribution: box = interquartile range (148.5–155.1 ms), median 150.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 (91.0 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	146.89
2	100	146.03
3	200	146.60
4	300	148.40
5	400	153.83
6	500	150.35
7	600	151.63
8	700	159.43
9	800	163.26
10	900	158.83
11	1000	150.71
12	1100	147.77
13	1200	154.15
14	1300	153.83
15	1400	150.19
16	1500	147.68
17	1600	152.38
18	1700	152.33
19	1800	148.29
20	1900	148.02
21	2000	148.88
22	2100	151.15
23	2200	148.21
24	2300	147.93
25	2400	157.09
26	2500	162.60
27	2600	155.15
28	2700	155.06
29	2800	148.87
30	2900	149.73
31	3000	147.36
32	3100	147.28
33	3200	150.17
34	3300	157.81
35	3400	149.96
36	3500	149.42
37	3600	167.08
38	3700	152.97
39	3800	148.79
40	3900	158.68
41	4000	150.23
42	4100	156.16
43	4200	149.77
44	4300	150.89
45	4400	148.02
46	4500	151.85
47	4600	181.51
48	4700	158.24
49	4800	152.25
50	4900	156.29

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.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Amsterdam (52.37403, 4.88969) and Hong Kong (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.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.

Stability & Trend

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

Round Statistic	Value
Minimum RTT	146.03 ms
Average RTT	152.8 ms
Maximum RTT	181.51 ms
Standard deviation	6.24 ms
Stdev / average	4.1%

RTT trend

Estimated route stability across the selected time window.

Average: 152.9 ms
Minimum: 151.3 ms
Maximum: 154.5 ms
Average loss: 0.02%

Route Context

Departure PoP: Amsterdam (AMS)
Destination PoP: Hong Kong (HKG)
Region overview: Europe → Asia Pacific
Corridor overview: Europe to Asia Pacific
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Hong Kong to Amsterdam latency and RTT — 154.3 ms

Fastest routes departing Amsterdam (AMS)

Amsterdam to London latency and RTT — 5.1 ms
Amsterdam to Frankfurt latency and RTT — 5.9 ms
Amsterdam to Paris latency and RTT — 7 ms
Amsterdam to Berlin latency and RTT — 7.2 ms
Amsterdam to Marseille latency and RTT — 19.7 ms

Fastest routes arriving at Hong Kong (HKG)

Taipei to Hong Kong latency and RTT — 15.4 ms
Singapore to Hong Kong latency and RTT — 30.9 ms
Tokyo to Hong Kong latency and RTT — 45.6 ms
Moscow to Hong Kong latency and RTT — 118.5 ms
Seattle to Hong Kong latency and RTT — 130.7 ms

Same corridor (Europe → Asia Pacific)

Moscow to Taipei latency and RTT — 130.9 ms
Marseille to Singapore latency and RTT — 138.5 ms
Berlin to Hong Kong latency and RTT — 143.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. 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-15T04:03:13Z, CC BY 4.0".

Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

Amsterdam, Netherlands → Hong Kong RTT