← 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 Tuesday, 10 November 2026 · astronomical night 18:40 → 05:29 (10.81 h) · Moon 3% (new moon) · weather: none — the schedule is astronomy only; overall conditions unknown

M42M42 17:05–22:50: unusableM42 22:50–23:25: marginalM42 23:25–05:30: goodM42 05:30–05:55: marginalM42 05:55–06:25: poorM42 06:25–07:10: unusableobserve M42 22:50–05:55scheduleM4218:0020: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
17:05–22:50 — nothing worth pointing at — 5.75
22:50–05:55 M42 7.08 0.78
05:55–07:10 — nothing worth pointing at — 1.25

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 89 unknown 23:25–05:30 (good) 42.9° at 02:35 143.0° 7.08

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