Rozhen Night Plan

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 Wednesday, 02 September 2026 · astronomical night 21:30 → 05:10 (7.67 h) · Moon 66% (waning gibbous) · 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

Schedule

local	target	hours	mean quality
19:50–06:50	— nothing worth pointing at —	11.0

Targets

target	astronomy	overall	best window	highest	Moon sep.	scheduled h
M45 Seven Sisters	28	0	—	72.5° at 06:20	7.7°	0.0

Left out

M45 — Overcast (≥80 % cloud) for 7.4 of 10.0 dark hours — the sky is closed whatever the geometry says.

💡 API

curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-09-02"

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"}.