← 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, 30 October 2026 · astronomical night 18:52 → 05:17 (10.43 h) · Moon 71% (waning gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 17:15–17:50: unusableM33 17:50–18:20: poorM33 18:20–18:55: marginalM33 18:55–02:45: goodM33 02:45–05:10: marginalM33 05:10–05:20: poorM33 05:20–06:55: unusableobserve M33 18:20–05:10scheduleM3318: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–18:20 — nothing worth pointing at — 1.08
18:20–05:10 M33 10.83 0.69
05:10–06:55 — nothing worth pointing at — 1.75

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 98 unknown 18:55–02:45 (good) 79.1° at 23:20 68.8° 10.83

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

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