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 Thursday, 03 September 2026 · astronomical night 21:28 → 05:12 (7.72 h) · Moon 55% (waning gibbous) · weather: ERA5 history
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 |
|---|---|---|---|
| 19:50–20:55 | — nothing worth pointing at — | 1.08 | |
| 20:55–04:00 | HD 189733 | 7.08 | 0.73 |
| 04:00–06:50 | — nothing worth pointing at — | 2.83 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| HD 189733 | 100 | 89 | 21:30–03:10 (good) | 71.1° at 22:30 | 106.2° | 7.08 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-09-03"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"}.