ForHosting KIT · Developer Utilities

Apsis speed ratio calculator

The apsis speed ratio calculator finds how many times faster an orbiting body moves at periapsis than at apoapsis.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter the eccentricity of an elliptical orbit and it evaluates (1 + e) / (1 - e), a dimensionless result that needs no mass, distance, or unit conversion. A circular orbit returns 1 because its speed is constant at every point. As eccentricity approaches 1, the contrast grows sharply. Values at or above 1 are rejected because those trajectories do not have both a periapsis and an apoapsis.

What the apsis speed ratio means

Periapsis is the point where an orbiting body is closest to the focus, while apoapsis is the point where it is farthest away. In a bound Keplerian orbit, the body travels fastest at periapsis and slowest at apoapsis. This calculator reports periapsis speed divided by apoapsis speed, so the result is always at least 1 for a valid elliptical orbit. A result of 3, for example, means the periapsis speed is three times the apoapsis speed; it does not mean either speed is three units per second. The ratio is dimensionless and describes contrast rather than an absolute velocity. Only eccentricity is needed because conservation of angular momentum makes the absolute scale and central mass cancel when the two apsis speeds are divided. That makes the result useful for comparing orbit shapes even when their sizes, periods, or central bodies differ. For a circular orbit, eccentricity is 0 and the two apsides coincide conceptually, producing a ratio of 1. Increasing eccentricity stretches the ellipse and increases the difference between the nearest-point and farthest-point speeds.

How the formula is obtained and evaluated

At either apsis, velocity is perpendicular to the radius vector. Specific angular momentum can therefore be written as periapsis radius times periapsis speed and also as apoapsis radius times apoapsis speed. Equating those expressions gives periapsis speed divided by apoapsis speed as apoapsis radius divided by periapsis radius. For an ellipse with semi-major axis a and eccentricity e, the apsis radii are a(1 + e) and a(1 - e). Dividing them cancels a and leaves the compact expression (1 + e) / (1 - e). The calculator validates the supplied eccentricity, performs that expression directly, and returns both the normalized input and the ratio. Numeric strings are accepted by the calculation layer for API convenience, although the published input contract uses a number. Results are rounded to fifteen significant digits so ordinary floating-point artifacts do not create unstable output while useful precision is retained. No ephemeris, gravitational parameter, or orbital distance is consulted. The computation is deterministic, uses no network request, and produces the same output for the same input in the browser and through the API.

Domain limits and interpreting extreme values

The accepted domain is 0 less than or equal to e and e less than 1. Negative eccentricity is not part of the standard geometric convention for Keplerian ellipses, so it is rejected rather than silently converted. An eccentricity of exactly 1 describes a parabolic trajectory, and a value greater than 1 describes a hyperbolic trajectory. Neither has a finite apoapsis, so a periapsis-to-apoapsis speed ratio is not defined for those cases and the calculator returns an input error. Near 1, the denominator 1 - e becomes very small and the ratio grows rapidly. This is mathematically expected, not an indication that an absolute speed has become infinite for a real engineered orbit. It means that the ideal two-body ellipse has a very large relative contrast between its apsis speeds. When using a value extremely close to 1, retain enough digits in the eccentricity because small rounding changes can materially affect the ratio. The formula also assumes an ideal two-body Keplerian ellipse. Perturbations, atmospheric drag, thrust, non-spherical gravity, and relativistic effects can change actual velocities, so mission-grade state prediction should use an appropriate orbit propagator rather than this shape-only ratio.

Compare elliptical orbit shapes

Turn eccentricities into an immediate speed-contrast measure without supplying a central mass or semi-major axis.

Check orbital mechanics coursework

Verify a hand calculation based on conservation of angular momentum and the two apsis radii.

Screen preliminary orbit concepts

Estimate how strongly speed varies between the nearest and farthest points before performing a full trajectory analysis.

What does the result represent?

It is periapsis speed divided by apoapsis speed. A result of 2.5 means the body moves 2.5 times faster at periapsis than at apoapsis.

Why does the calculator need only eccentricity?

When the two apsis speeds are divided, the central mass and semi-major axis cancel, leaving only (1 + e) / (1 - e).

What happens for a circular orbit?

With eccentricity 0, the result is 1. The orbital speed has no periapsis-to-apoapsis contrast in a circle.

Why are eccentricities of 1 or greater rejected?

Parabolic and hyperbolic trajectories have no finite apoapsis, so the requested ratio between two apsis speeds is undefined.

Does this calculate either absolute orbital speed?

No. Absolute speed requires additional data such as the gravitational parameter and an orbital distance or semi-major axis.

How much does an API calculation cost?

Each 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/astro/apsis-speed-ratio

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/astro/apsis-speed-ratio \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"eccentricity":0.5}'
{
  "eccentricity": 0.5
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "astro.apsis_speed_ratio",
  "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 →