Hubble Sat Spotter

--:--:--Live
Next pass computing…

Looking down drag to spin, click to move

Looking up the sky above the observer

now+12h+24h+36h+48h+60h+72h
Min elevation How high above the horizon a pass must peak before the device SDK schedules a transmission for it. Higher passes give a shorter, stronger link but come less often. SDK default is 45°, allowed range 30–90°. Shown as the dashed ring on the sky chart. 45°

Pass Planning next 72 hours, passes peaking above 10°

SatelliteRisePeakSetMax elSDK TX window (160 s)SDK

Orbits are propagated in your browser with SGP4 from Hubble's published TLEs. Using the built-in snapshot from Oct 8, 2026. Elements more than a few days old drift by seconds to minutes.

"SDK" marks passes the device SDK's hubble_sat_next_pass_get() would schedule at the current minimum elevation (default 45°, allowed 30–90°). Its window is 8 retries × 20 s = 160 s centered on the peak. A cross-check of the SDK code against SGP4 for Durham agreed to within about 15 s on peak time.

The sat-continuous firmware transmits every 10 s regardless, so any pass above the horizon is a chance for a packet to land. Higher passes mean a shorter path and a stronger link.