← 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, 06 November 2026 · astronomical night 18:44 → 05:25 (10.68 h) · Moon 6% (waning crescent) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 17:05–17:40: unusableM33 17:40–18:15: poorM33 18:15–18:45: marginalM33 18:45–04:25: goodM33 04:25–04:55: marginalM33 04:55–07:05: unusableobserve M33 18:15–04:55scheduleM3318: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–18:15 — nothing worth pointing at — 1.17
18:15–04:55 M33 10.67 0.9
04:55–07:05 — nothing worth pointing at — 2.17

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 100 unknown 18:45–04:25 (good) 79.1° at 22:50 157.8° 10.67

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

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