# Berlin, Germany → Amsterdam, Netherlands RTT

🇩🇪 **Berlin, Germany (BER)** → 🇳🇱 **Amsterdam, Netherlands (AMS)**

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

During the 2026-08-16T04:07:28Z measurement round, ICMP probes from Berlin, Germany to Amsterdam, Netherlands averaged 7.2 ms round-trip time, with all 50 samples between 6.91 ms and 7.91 ms. The 0.23 ms standard deviation, 0.22 ms jitter, and 0% packet loss together define an Ultra-Low latency path that stayed consistent throughout the window.

Relative to the 579.2 km geodesic distance, the measured average is 1.27 times the fiber floor of 5.67 ms, for a fiber efficiency of 78.8%. The gap between the measured RTT and the fiber floor is 1.53 ms, leaving a short international route with a small absolute overhead while staying close to the theoretical propagation budget.

This route ranked 2nd in the 19-route measurement set for this network, placing it in the fastest tier. Its own spread-to-average ratio is about 3.2%, close to the 3.28% median across the set, so the low average was not achieved at the expense of stability. The route-specific value is an Ultra-Low RTT with near-floor efficiency and no packet loss.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **7.2 ms**                                     |
| Jitter               | **0.22 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **5.67 ms**                                    |
| Fiber Efficiency     | **78.8%**                                      |
| 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 [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) 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                      | **579.2 km** |
| Vacuum RTT floor                              | **3.86 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **5.67 ms**  |
| Low-latency fiber material floor              | **5.65 ms**  |
| Engineering floor (5% path allowance)         | **5.96 ms**  |
| Research 1.33× mapped-fiber reference         | **7.54 ms**  |
| Estimated unamplified path loss               | **121.6 dB** |
| Transparent optical spans / inline amplifiers | **8 / 7**    |
| Published RTT inflation over fiber floor      | **1.27×**    |

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        | **6.91 ms** |
| Average RTT        | **7.2 ms**  |
| Maximum RTT        | **7.91 ms** |
| Standard deviation | **0.23 ms** |
| Stdev / average    | **3.2%**    |

## Route Context

* Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* 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 Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms

**Fastest routes departing Berlin (BER)**

* [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms
* [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms
* [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms
* [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms
* [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms

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

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