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 January 2026 · astronomical night 18:48 → 06:08 (11.32 h) · Moon 47% (last quarter) · weather: ERA5 history
Each row is the target's quality through the night, white → amber → green for 0 → 0.3 → 0.6 → 1 (the same thresholds as poor / marginal / good). Dark blue: the schedule. Grey columns: twilight. Download: schedule CSV · targets CSV · JSON
| local | target | hours | mean quality |
|---|---|---|---|
| 17:05–21:00 | — nothing worth pointing at — | 3.92 | |
| 21:00–23:00 | M33 | 2.0 | 0.72 |
| 23:00–07:50 | — nothing worth pointing at — | 8.83 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| M33 Triangulum Pinwheel | 100 | 33 | 21:00–22:00 (good) | 79.1° at 18:35 | 161.7° | 2.0 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-01-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"}.