ForHosting KIT · Developer Utilities

Sidereal drift rate calculator

The sidereal drift rate calculator estimates how quickly a star moves across a stationary telescope's field of view as Earth rotates.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter the star's declination from -90° to +90°, and the calculator applies 15 arcseconds per second multiplied by the cosine of declination. The result is useful for drift alignment, eyepiece timing, detector planning, and understanding why stars near the celestial poles appear to move more slowly than stars near the celestial equator.

What sidereal drift rate means

A telescope that is not tracking stays fixed relative to the ground while the celestial sphere appears to turn because Earth rotates. Near the celestial equator, a star crosses the sky at approximately 15 arcseconds each second of time. Declination changes the component of that apparent motion along a circle of constant declination. A star at zero degrees declination receives the full 15 arcseconds-per-second rate, while a star closer to either celestial pole traces a smaller circle and therefore moves more slowly across the field. This calculator reports that projected angular rate. It is a sky-coordinate rate, not the star's physical velocity through space, and it does not depend on stellar distance. The sign of declination identifies the northern or southern celestial hemisphere, but the cosine is symmetric, so equal positive and negative declinations have equal drift-rate magnitudes. At either pole, the idealized projected rate reaches zero because the star lies on the rotation axis of the apparent celestial sphere.

How the calculation works

The calculation uses the relation r = 15 cos(δ), where r is the drift rate in arcseconds per second and δ is declination in degrees. Internally, the declination is converted to radians before evaluating the cosine, because standard trigonometric functions operate in radians. For example, a declination of 60° has a cosine of 0.5, giving a drift rate of 7.5 arcseconds per second. A declination of -60° produces the same result. Inputs at -90° and +90° are accepted and return zero, while any value below -90° or above +90° is rejected because it is not a valid astronomical declination. The returned value is rounded to twelve decimal places to keep browser and API results stable. The constant 15 is the conventional mean sidereal rate expressed to the precision intended by this tool; it is not a higher-precision Earth rotation model and does not include small observational corrections.

Using the result in observing plans

Drift rate becomes practical when you combine it with an angular field dimension. Dividing a field width in arcseconds by the returned arcseconds-per-second value gives an approximate crossing time for a star moving through that dimension, provided the geometry is aligned with the drift direction. That estimate can help you choose a detector window, anticipate how long an unguided target remains visible, or compare drift-alignment measurements made with stars at different declinations. Near a celestial pole, take care: the rate becomes very small, crossing times become very long, and field orientation or measurement error can dominate a simple estimate. This calculator also does not correct for atmospheric refraction, polar misalignment, tracking motor errors, precession, nutation, or a star's proper motion. Use the output as the ideal sidereal contribution from declination alone. For automated calls, each calculation costs $0.002; the same deterministic arithmetic can also run locally in the browser without sending observational details elsewhere.

Estimate field crossing time

Use the angular drift rate with an eyepiece or sensor field width to estimate how long a star remains in view without tracking.

Plan drift alignment

Compare ideal rates for candidate alignment stars and understand how declination changes the apparent motion being measured.

Prepare detector observations

Estimate the expected sidereal motion across pixels after converting the detector's angular scale to arcseconds.

What formula does the calculator use?

It uses drift rate = 15 × cos(declination), with declination converted from degrees to radians and the result reported in arcseconds per second.

What declination values are valid?

Any finite value from -90° through +90°, inclusive. Values outside that astronomical range return an invalid-input error.

Why do positive and negative declinations give the same rate?

Cosine is symmetric around zero, so stars equally far north and south of the celestial equator have the same drift-rate magnitude.

Why is the rate zero at the celestial poles?

The poles lie on the apparent rotation axis. In this ideal projection, their circles of constant declination shrink to a point, so the drift rate is zero.

Does this include tracking errors or atmospheric refraction?

No. It calculates only the ideal declination-dependent sidereal drift and does not model equipment errors, refraction, precession, nutation, or proper motion.

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/sidereal-drift-rate

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/sidereal-drift-rate \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"declination_deg":30}'
{
  "declination_deg": 30
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "astro.sidereal_drift_rate",
  "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 →