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 Friday, 18 September 2026 · astronomical night 20:59 → 05:31 (8.53 h) · Moon 51% (first quarter) · 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:25–20:30 | — nothing worth pointing at — | 1.08 | |
| 20:30–03:05 | HD 189733 | 6.58 | 0.67 |
| 03:05–07:10 | — nothing worth pointing at — | 4.08 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| HD 189733 | 100 | 83 | 21:00–02:35 (good) | 71.1° at 21:30 | 60.4° | 6.58 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-09-18"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"}.