How to measure connection consistency on a train

Your connection works at the station, then pauses or drops out once the train is moving. A speed test at one moment may look fine and still miss those brief interruptions.

Use the Connection Stability test to check response time, jitter, lost requests and dropouts over a few minutes. Repeat it separately on train Wi-Fi and mobile data to see which connection holds up better along your route.

Measure the connection during the ride

1. Open the Connection Stability test on the device and browser you plan to use. Connect to one network, such as the train's Wi-Fi or your phone's mobile data, and make sure a regular web page loads.
2. If you are using onboard Wi-Fi, complete its sign-in or captive portal page first. A network can show as connected while still blocking internet access until you accept the terms or sign in.
3. Start the stability check and let it run for a few minutes while the train is moving. Keep the browser tab open. For a useful baseline, pause downloads, video streams and large file uploads during the measurement.
4. Note the time, approximate location or route segment, network used, and the test's response time, jitter, lost requests and dropouts. The test does not necessarily keep a travel log, so write down results you want to compare.
5. Run another measurement later on the same network. If you want to compare onboard Wi-Fi with mobile data, switch networks between separate runs rather than changing midway through one test.

Try to compare similar parts of the ride, such as two stretches between stops. Conditions can change quickly as the train moves, so one short result is only a snapshot, not a verdict on the whole route.

What the result means

Response time stays low and steady, with no lost requests

The connection is responding consistently during that stretch. This does not guarantee that every app or website will be fast, but it suggests that requests to the test server are getting through without obvious delays or interruptions.

Response time jumps or jitter is high

Jitter means the response time varies from one request to the next. A changing result can make calls sound uneven or games feel inconsistent even if the average response time looks acceptable. On a train, changing coverage or a handoff between network connections may be involved.

The test reports lost requests or dropouts

Some requests did not get a timely response, or the connection paused during the check. If this happens in the same route segment on repeated runs, that stretch may have unreliable coverage. It does not prove whether the cause is the train's Wi-Fi, the cellular network, your device, or the path between them.

The test is steady, but one app still stalls

The connection to the test server may be working while a particular app or service has its own problem. Check whether other sites work at the same time, and whether the app reconnects after a short pause. A browser test cannot diagnose every service's server or network path.

How to improve the connection

1. Finish the onboard Wi-Fi sign-in. Open a new browser tab and look for a sign-in or terms page. If it does not appear, disconnect and reconnect to the train's Wi-Fi, then try loading a non-sensitive page to check that internet access is available.
2. Pause other network activity. Stop large downloads, cloud backups and video streams during the test. On Windows 11, check Settings › Network & internet for the active connection. On macOS, check System Settings › Wi-Fi. A busy connection can add delay and make results harder to compare.
3. Compare Wi-Fi and mobile data separately. If onboard Wi-Fi is unstable, test your phone's cellular connection as a separate run, if your plan and reception allow it. On iPhone, check Settings › Cellular; on Android, open Settings › Network & internet › Internet (the wording can vary by phone). Avoid switching networks while a test is running.
4. Reconnect to the same network. Turn Wi-Fi off and on, then reconnect and complete any sign-in page again. On Windows 11, use Settings › Network & internet › Wi-Fi. On macOS, use System Settings › Wi-Fi. On a phone, use Settings › Wi-Fi on iPhone or the Wi-Fi controls under Settings › Network & internet on many Android phones.
5. Keep comparison conditions consistent. Leave your VPN, browser and device in the same state for each run. A VPN can change the route your traffic takes, so results with it on may differ from results with it off. Do not turn off a work VPN if your organization requires it.
6. Restart the device only if problems continue. A restart can clear a stuck network connection, but it will not fix a coverage gap along the route. Save your notes first, reconnect, and repeat the test when service returns.

Why train results change from one minute to the next

A moving train can pass between cellular coverage areas or switch between onboard access points. Either change can briefly interrupt requests. Train Wi-Fi may also rely on a cellular or satellite connection beyond the carriage, so a strong Wi-Fi connection between your device and the train's router does not guarantee a steady internet connection outside the train.

The test measures how requests behave over the connection. It does not read Wi-Fi signal strength in dBm, identify which access point you are connected to, or show exactly where along the route a delay occurred. Compare repeated results and treat them as evidence about connection quality, not a precise map of the cause.

If you need a reliable connection for a call or upload, run the test before the task and again during the ride. A few measurements can show whether the problem is limited to one stretch or continues throughout the trip.