← 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 Friday, 09 October 2026 · astronomical night 20:21 → 05:55 (9.55 h) · Moon 1% (new moon) · weather: forecast

M42M42 18:45–02:00: unusableM42 02:00–02:35: marginalM42 02:35–03:00: goodM42 03:00–06:00: marginalM42 06:00–07:00: poorM42 07:00–07:30: unusableobserve M42 02:00–06:00scheduleM4220: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
18:45–02:00 — nothing worth pointing at — 7.25
02:00–06:00 M42 4.0 0.47
06:00–07:30 — nothing worth pointing at — 1.5

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 77 44 02:35–03:00 (good) 42.9° at 05:45 101.3° 4.0

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

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