← 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, 20 October 2026 · astronomical night 20:05 → 06:07 (10.03 h) · Moon 71% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M31M31 18:30–19:05: unusableM31 19:05–19:35: poorM31 19:35–20:10: marginalM31 20:10–06:10: goodM31 06:10–06:15: marginalM31 06:15–06:50: poorM31 06:50–07:40: unusableobserve M31 19:35–06:15scheduleM3120: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
18:30–19:35 — nothing worth pointing at — 1.08
19:35–06:15 M31 10.67 0.77
06:15–07:40 — nothing worth pointing at — 1.42

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 100 unknown 20:10–06:10 (good) 89.5° at 00:10 69.9° 10.67

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

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