← 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, 01 October 2026 · astronomical night 20:35 → 05:46 (9.18 h) · Moon 68% (waning gibbous) · weather: ERA5 history

VegaVega 19:00–21:00: unusableVega 21:00–01:45: marginalVega 01:45–01:50: poorVega 01:50–07:20: unusableobserve Vega 21:00–01:45scheduleVega20: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:00–21:00 — nothing worth pointing at — 2.0
21:00–01:45 Vega 4.75 0.44
01:45–07:20 — nothing worth pointing at — 5.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 100 47 21:00–01:45 (marginal) 87.1° at 19:15 109.9° 4.75

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

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