← 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, 22 September 2026 · astronomical night 20:51 → 05:35 (8.73 h) · Moon 85% (waxing gibbous) · weather: ERA5 history

M31M31 19:15–22:00: unusableM31 22:00–23:00: poorM31 23:00–03:00: unusableM31 03:00–04:00: marginalM31 04:00–05:40: goodM31 05:40–06:10: marginalM31 06:10–06:45: poorM31 06:45–07:10: unusableobserve M31 03:00–06:10scheduleM3120: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
19:15–03:00 — nothing worth pointing at — 7.75
03:00–06:10 M31 3.17 0.68
06:10–07:10 — nothing worth pointing at — 1.0

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 100 32 04:00–05:40 (good) 89.5° at 02:00 76.7° 3.17

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

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