← 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 Friday, 29 September 2028 · astronomical night 20:38 → 05:44 (9.11 h) · Moon 88% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

VegaVega 19:35–20:10: quality 0.1Vega 20:10–20:40: quality 0.3Vega 20:40–23:45: quality 0.6Vega 23:45–01:10: quality 0.5Vega 01:10–01:35: quality 0.4Vega 01:35–01:55: quality 0.3observe Vega 20:10–01:45scheduleVega20: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:05–20:10 — nothing worth pointing at — 1.08
20:10–01:45 Vega 5.58 0.53
01:45–07:20 — nothing worth pointing at — 5.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
Vega Vega 49 unknown 20:40–22:30 (good) 87.1° at 19:25 66.3° 5.58

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

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