← single target

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 Monday, 14 September 2026 · astronomical night 21:07 → 05:26 (8.32 h) · Moon 15% (waxing crescent) · weather: ERA5 history

M45M45 19:30–00:00: unusableM45 00:00–00:35: marginalM45 00:35–02:00: goodM45 02:00–02:15: marginalM45 02:15–03:00: goodM45 03:00–07:05: unusableobserve M45 00:00–03:00scheduleM4520:0022:0000:0002:0004:0006:00

Faded bands: each target's own windows (green good, amber marginal, pink poor). Dark blue: the schedule. Grey columns: twilight.

Schedule

localtargethoursmean quality
19:30–00:00 — nothing worth pointing at — 4.5
00:00–03:00 M45 3.0 0.64
03:00–07:05 — nothing worth pointing at — 4.08

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M45 Seven Sisters 100 37 00:35–02:00 (good) 72.5° at 05:35 158.5° 3.0

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

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