← 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, 15 September 2026 · astronomical night 21:05 → 05:27 (8.37 h) · Moon 23% (waxing crescent) · weather: ERA5 history

VegaVega 19:30–20:00: unusableVega 20:00–21:10: poorVega 21:10–22:00: marginalVega 22:00–23:30: goodVega 23:30–02:50: marginalVega 02:50–07:05: unusableobserve Vega 21:10–02:50scheduleVega20: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:30–21:10 — nothing worth pointing at — 1.67
21:10–02:50 Vega 5.67 0.57
02:50–07:05 — nothing worth pointing at — 4.25

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 100 62 22:00–23:30 (good) 87.1° at 20:20 78.9° 5.67

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

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