← 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, 02 October 2026 · astronomical night 20:33 → 05:47 (9.23 h) · Moon 57% (waning gibbous) · weather: ERA5 history

M42M42 19:00–02:25: unusableM42 02:25–02:35: poorM42 02:35–05:50: marginalM42 05:50–06:55: poorM42 06:55–07:20: unusableobserve M42 02:35–05:50scheduleM4220: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:00–02:35 — nothing worth pointing at — 7.58
02:35–05:50 M42 3.25 0.47
05:50–07:20 — nothing worth pointing at — 1.5

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 22 22 02:35–05:50 (marginal) 42.9° at 06:10 34.0° 3.25

💡 API
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-10-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"}.