← 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, 30 August 2028 · astronomical night 21:35 → 05:07 (7.53 h) · Moon 86% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

VegaVega 20:30–21:00: quality 0.1Vega 21:00–21:40: quality 0.3Vega 21:40–22:00: quality 0.7Vega 22:00–22:45: quality 0.6Vega 22:45–00:30: quality 0.7Vega 00:30–03:00: quality 0.6Vega 03:00–03:05: quality 0.5Vega 03:05–03:15: quality 0.7Vega 03:15–03:30: quality 0.6Vega 03:30–03:45: quality 0.5Vega 03:45–03:50: quality 0.4observe Vega 21:00–03:50scheduleVega20:0022:0000:0002:0004:0006:00

Each row is the target's quality through the night, white → amber → green for 0 → 0.3 → 0.6 → 1 (the same thresholds as poor / marginal / good). Dark blue: the schedule. Grey columns: twilight.  Download: schedule CSV · targets CSV · JSON

Schedule

localtargethoursmean quality
19:55–21:00 — nothing worth pointing at — 1.08
21:00–03:50 Vega 6.83 0.6
03:50–06:50 — nothing worth pointing at — 3.0

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 68 unknown 21:40–02:40 (good) 87.1° at 21:20 62.0° 6.83

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

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"}; an unreadable date → 400 {"error", "code": "invalid_date"}.