← 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 Saturday, 10 October 2026 · astronomical night 20:20 → 05:56 (9.6 h) · Moon 0% (new moon) · weather: forecast

VegaVega 18:45–19:20: unusableVega 19:20–19:50: poorVega 19:50–20:25: marginalVega 20:25–00:40: goodVega 00:40–01:15: marginalVega 01:15–07:30: unusableobserve Vega 19:50–01:15scheduleVega20: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:45–19:50 — nothing worth pointing at — 1.08
19:50–01:15 Vega 5.42 0.75
01:15–07:30 — nothing worth pointing at — 6.25

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 100 92 20:25–00:40 (good) 87.1° at 18:40 91.0° 5.42

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

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