← 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, 10 September 2027 · astronomical night 21:15 → 05:21 (8.09 h) · Moon 79% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

HD 189733HD 189733 20:10–20:45: quality 0.1HD 189733 20:45–21:20: quality 0.3HD 189733 21:20–23:50: quality 0.6HD 189733 23:50–00:10: quality 0.7HD 189733 00:10–02:10: quality 0.6HD 189733 02:10–02:50: quality 0.8HD 189733 02:50–03:05: quality 0.7HD 189733 03:05–03:20: quality 0.6HD 189733 03:20–03:30: quality 0.5HD 189733 03:30–03:40: quality 0.4observe HD 189733 20:45–03:40scheduleHD 18973320: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:35–20:45 — nothing worth pointing at — 1.17
20:45–03:40 HD 189733 6.92 0.62
03:40–07:00 — nothing worth pointing at — 3.33

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
HD 189733 84 unknown 21:20–03:10 (good) 71.1° at 22:05 46.1° 6.92

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

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