Up to ten targets, one night: each gets its good/marginal/poor windows (darkness × altitude × Moon × clouds, as on the single-target page), then the night is handed out five minutes at a time to whichever target is best — with hysteresis, so you get a few solid blocks of at least 30 minutes, not a flicker. Targets that never win a block are listed with the reason.
Try: an autumn deep-sky night · ← previous night · next night →
Night of Saturday, 10 October 2026 · astronomical night 20:20 → 05:56 (9.6 h) · Moon 0% (new moon) · weather: forecast
Faded bands: each target's own windows (green good, amber marginal, pink poor). Dark blue: the schedule. Grey columns: twilight.
| local | target | hours | mean quality |
|---|---|---|---|
| 18:45–01:55 | — nothing worth pointing at — | 7.17 | |
| 01:55–06:30 | M42 | 4.58 | 0.72 |
| 06:30–07:30 | — nothing worth pointing at — | 1.0 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| M42 Great Orion Nebula | 78 | 75 | 02:25–06:00 (good) | 42.9° at 05:40 | 112.0° | 4.58 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-10-10"targets: names or RA Dec, separated by commas, semicolons or newlines, at most ten. The response carries targets[] (score, verdict, best_window, windows, transit, moon_separation), schedule[] (blocks with target, start/end in UTC and local, hours, mean_quality; target: null is idle time), unscheduled[] with a why, forecast_source, warnings[]. Missing targets → 400 {"error", "code": "targets_missing"}; an unreadable date → 400 {"error", "code": "invalid_date"}.