← 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 Sunday, 04 October 2026 · astronomical night 20:30 → 05:49 (9.32 h) · Moon 35% (waning crescent) · weather: forecast

VegaVega 18:55–19:30: unusableVega 19:30–20:00: poorVega 20:00–20:35: marginalVega 20:35–01:05: goodVega 01:05–01:35: marginalVega 01:35–07:25: unusableobserve Vega 20:00–01:35scheduleVega20: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:55–20:00 — nothing worth pointing at — 1.08
20:00–01:35 Vega 5.58 0.82
01:35–07:25 — nothing worth pointing at — 5.83

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 100 100 20:35–01:05 (good) 87.1° at 19:05 114.8° 5.58

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

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