ForHosting KIT · Developer Utilities

Time to waypoint at knots calculator

This time to waypoint calculator converts a remaining distance in nautical miles and a current speed over ground in knots into a clear travel duration.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

It returns hours, minutes, seconds, and a readable duration without requiring coordinates, a route service, or a departure time. The calculation is useful for sailors, navigators, dispatchers, and developers who already know the distance to go and need a reproducible estimate based on present speed. Every result is deterministic and uses the direct nautical relationship between knots and nautical miles per hour.

Enter the remaining nautical miles and current speed

Start with the distance still to travel to the active waypoint, expressed in nautical miles, and the vessel's current speed over ground, expressed in knots. Use distance from your chartplotter, navigation software, route plan, or a separately measured leg. Speed over ground is the appropriate input because it describes actual movement across the earth rather than speed through the water. Current, tide, wind, steering, and sea state may make those two speeds differ. The calculator accepts zero distance, which correctly produces a zero duration when the waypoint has already been reached, but speed must be greater than zero because division by zero cannot produce a finite arrival estimate. Decimal values are welcome, so a distance such as 12.75 nautical miles and a speed of 6.4 knots can be used directly. Choose the precision only to control displayed numeric rounding; it does not alter the underlying division. For a useful operational estimate, copy both figures from measurements taken at roughly the same moment. Mixing an old distance with a new speed, or the reverse, can make a mathematically correct answer operationally misleading.

Understand the nautical-mile and knot formula

One knot means one nautical mile per hour, so the core calculation is simply remaining nautical miles divided by speed in knots. A vessel with 24 nautical miles left while making 8 knots has 3 hours of travel remaining if that speed continues. The response provides the same duration in decimal hours, decimal minutes, decimal seconds, and a compact day-hour-minute-second label. This makes the output convenient for a bridge display, a log entry, an alert threshold, or an application that needs seconds for later processing. Numeric fields are rounded to the requested number of decimal places for stable output, while the readable label rounds the computed duration to the nearest whole second. No clock is consulted, so the result is time remaining rather than a time of day or an arrival timestamp. If you need an estimated arrival clock time, add the returned seconds to a trusted timestamp in your own system. Keeping duration separate avoids hidden assumptions about time zones, daylight saving rules, device clocks, and the exact moment at which the input was observed.

Use the estimate safely as conditions change

The result assumes the supplied speed over ground remains constant and that the supplied distance represents the path still to be traveled. Real voyages rarely hold both values perfectly steady. Course changes, traffic separation schemes, tacking, currents, weather, speed restrictions, maneuvering, and route revisions can all change the actual arrival time. Recalculate whenever the navigation display reports a meaningful change in distance or speed, and treat the answer as a current projection rather than a promise. For noisy speed readings, your application may use a short moving average before calling the calculator, provided that averaging method fits the operational context. Do not substitute speed through water unless you intentionally want a through-water estimate; speed over ground already reflects current and is normally the better value for progress toward a geographic waypoint. Also confirm that distance is in nautical miles rather than statute miles or kilometres. This capability performs no automatic unit conversion because explicit nautical inputs prevent silent mistakes. It does not inspect heading or determine whether the vessel is moving toward the waypoint, so upstream navigation equipment remains responsible for supplying a valid remaining route distance and meaningful current speed.

Marine passage monitoring

Turn chartplotter distance-to-go and current speed over ground into a readable remaining duration.

Fleet telemetry dashboards

Calculate consistent waypoint countdown values from incoming nautical-mile and knot measurements.

Voyage planning checks

Compare travel durations at several proposed constant speeds without consulting a map or clock.

What formula does the calculator use?

It divides distance remaining in nautical miles by speed over ground in knots because one knot equals one nautical mile per hour.

Can the remaining distance be zero?

Yes. Zero nautical miles returns a zero duration, representing a waypoint that has already been reached.

Why must speed be greater than zero?

A zero or negative speed cannot produce a finite forward travel time, so it is rejected as invalid input.

Does this return an arrival clock time?

No. It returns time remaining and does not read a clock. Add the returned seconds to a trusted timestamp if you need an arrival time.

Does it account for current or wind?

It does not model them separately. Use speed over ground, which already reflects their net effect on measured ground progress at that moment.

What does an API calculation cost?

Each completed API request costs $0.002. The same deterministic calculation can also run in the browser.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/travel/time-to-waypoint

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/travel/time-to-waypoint \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"distance_nm":24.5,"speed_knots":7}'
{
  "distance_nm": 24.5,
  "speed_knots": 7
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "travel.time_to_waypoint",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →