← 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, 30 October 2026 · astronomical night 18:52 → 05:17 (10.43 h) · Moon 71% (waning gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

HD 189733HD 189733 17:15–17:50: unusableHD 189733 17:50–18:20: poorHD 189733 18:20–18:55: marginalHD 189733 18:55–22:45: goodHD 189733 22:45–23:20: marginalHD 189733 23:20–06:55: unusableobserve HD 189733 18:20–23:20scheduleHD 18973318:0020: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
17:15–18:20 — nothing worth pointing at — 1.08
18:20–23:20 HD 189733 5.0 0.79
23:20–06:55 — nothing worth pointing at — 7.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
HD 189733 100 unknown 18:55–22:45 (good) 71.1° at 17:45 128.2° 5.0

💡 API
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-10-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"}.