← 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 Sunday, 18 October 2026 · astronomical night 20:07 → 06:04 (9.95 h) · Moon 52% (first quarter) · weather: none — the schedule is astronomy only; overall conditions unknown

M31M31 18:35–19:05: unusableM31 19:05–19:40: poorM31 19:40–20:10: marginalM31 20:10–06:05: goodM31 06:05–06:25: marginalM31 06:25–06:55: poorM31 06:55–07:40: unusableobserve M31 19:40–06:25scheduleM3120: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:35–19:40 — nothing worth pointing at — 1.08
19:40–06:25 M31 10.75 0.87
06:25–07:40 — nothing worth pointing at — 1.25

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 100 unknown 20:10–06:05 (good) 89.7° at 00:15 91.1° 10.75

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

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