# Frankfurt, Germany → Amsterdam, Netherlands RTT

🇩🇪 **Frankfurt, Germany (FRA)** → 🇳🇱 **Amsterdam, Netherlands (AMS)**

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

The 2026-08-16T04:07:28Z round shows ICMP echo RTT from Frankfurt, Germany to Amsterdam, Netherlands averaging 5.9 ms across 50 samples at 100 ms intervals, with a minimum of 5.62 ms, a maximum of 6.84 ms, and zero packet loss.

For the 365.1 km great-circle distance, the fiber-floor RTT is 3.57 ms, so the measured average is 1.65 times that floor, an efficiency of 60.6% and an ultra-low latency tier. The tiny standard deviation of 0.25 ms and jitter of 0.17 ms indicate an exceptionally consistent path.

This is the fastest of the 19 outbound routes measured from Frankfurt, and the standard deviation is about 4.2% of the average, slightly above the 3.28% median variability seen across the network's measured routes. In practical terms, the route's round-trip time rarely moves by more than a fraction of a millisecond, so it can serve as a stable reference point for regional measurements.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **5.9 ms**                                     |
| Jitter               | **0.17 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **3.57 ms**                                    |
| Fiber Efficiency     | **60.6%**                                      |
| Latency Tier         | Ultra-Low                                      |
| Source Region        | [Europe](/docs/network/latency/regions/europe) |
| 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 [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address.

| Physical Reference                            | Value        |
| --------------------------------------------- | ------------ |
| WGS-84 geodesic distance                      | **365.1 km** |
| Vacuum RTT floor                              | **2.44 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **3.57 ms**  |
| Low-latency fiber material floor              | **3.56 ms**  |
| Engineering floor (5% path allowance)         | **3.75 ms**  |
| Research 1.33× mapped-fiber reference         | **4.75 ms**  |
| Estimated unamplified path loss               | **76.7 dB**  |
| Transparent optical spans / inline amplifiers | **5 / 4**    |
| Published RTT inflation over fiber floor      | **1.65×**    |

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        | **5.62 ms** |
| Average RTT        | **5.9 ms**  |
| Maximum RTT        | **6.84 ms** |
| Standard deviation | **0.25 ms** |
| Stdev / average    | **4.2%**    |

## Route Context

* Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [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**

* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms

**Fastest routes departing Frankfurt (FRA)**

* [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms
* [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms
* [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms
* [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms
* [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms

**Fastest routes arriving at Amsterdam (AMS)**

* [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms
* [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms
* [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms
* [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms
* [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms

**Same corridor (Europe → Europe)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms
* [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 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/fra-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Amsterdam 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/fra-ams-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.