← 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 Thursday, 29 October 2026 · astronomical night 18:53 → 05:16 (10.39 h) · Moon 81% (waning gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M45M45 17:15–20:05: unusableM45 20:05–20:10: poorM45 20:10–05:20: marginalM45 05:20–06:25: poorM45 06:25–06:55: unusableobserve M45 20:10–05:20scheduleM4518: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:15–20:10 — nothing worth pointing at — 2.92
20:10–05:20 M45 9.17 0.41
05:20–06:55 — nothing worth pointing at — 1.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M45 Seven Sisters 48 unknown 20:10–05:20 (marginal) 72.5° at 01:35 27.7° 9.17

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

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