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, 05 September 2026 · astronomical night 21:24 → 05:14 (7.83 h) · Moon 32% (waning crescent) · 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:45–20:50 | — nothing worth pointing at — | 1.08 | |
| 20:50–03:55 | HD 189733 | 7.08 | 0.86 |
| 03:55–06:55 | — nothing worth pointing at — | 3.0 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| HD 189733 | 100 | 100 | 21:25–03:25 (good) | 71.1° at 22:25 | 124.1° | 7.08 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-09-05"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"}.