← 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 Wednesday, 11 November 2026 · astronomical night 18:40 → 05:30 (10.84 h) · Moon 7% (waxing crescent) · weather: none — the schedule is astronomy only; overall conditions unknown

VegaVega 17:00–17:35: unusableVega 17:35–18:10: poorVega 18:10–18:45: marginalVega 18:45–21:35: goodVega 21:35–22:05: marginalVega 22:05–07:10: unusableobserve Vega 18:10–22:05scheduleVega18: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:00–18:10 — nothing worth pointing at — 1.17
18:10–22:05 Vega 3.92 0.75
22:05–07:10 — nothing worth pointing at — 9.08

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 73 unknown 18:45–21:35 (good) 87.1° at 15:35 69.4° 3.92

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

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