← 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 Sunday, 25 October 2026 · astronomical night 18:58 → 05:12 (10.24 h) · Moon 100% (full moon) · weather: none — the schedule is astronomy only; overall conditions unknown

M42M42 17:25–23:55: unusableM42 23:55–00:35: poorM42 00:35–05:15: marginalM42 05:15–06:20: poorM42 06:20–06:50: unusableobserve M42 00:35–05:15scheduleM4218: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:25–00:35 — nothing worth pointing at — 7.17
00:35–05:15 M42 4.67 0.45
05:15–06:50 — nothing worth pointing at — 1.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 32 unknown 00:35–05:15 (marginal) 42.9° at 03:40 61.4° 4.67

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

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