← 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 Thursday, 10 September 2026 · astronomical night 21:14 → 05:21 (8.11 h) · Moon 0% (new moon) · weather: ERA5 history

VegaVega 19:35–20:10: unusableVega 20:10–20:45: poorVega 20:45–21:15: marginalVega 21:15–02:40: goodVega 02:40–03:10: marginalVega 03:10–07:00: unusableobserve Vega 20:45–03:10scheduleVega20: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:35–20:45 — nothing worth pointing at — 1.17
20:45–03:10 Vega 6.42 0.85
03:10–07:00 — nothing worth pointing at — 3.83

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 100 99 21:15–02:40 (good) 87.1° at 20:40 104.9° 6.42

💡 API
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-09-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"}.