← 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 Saturday, 03 June 2028 · astronomical night 22:58 → 03:40 (4.71 h) · Moon 87% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M31M31 02:35–02:50: quality 0.4M31 02:50–03:10: quality 0.5M31 03:10–03:15: quality 0.6M31 03:15–03:35: quality 0.7M31 03:35–03:45: quality 0.8M31 03:45–04:35: quality 0.4M31 04:35–05:15: quality 0.1observe M31 02:35–04:35scheduleM3122:0000:0002:0004: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
20:50–02:35 — nothing worth pointing at — 5.75
02:35–04:35 M31 2.0 0.52
04:35–05:50 — nothing worth pointing at — 1.25

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 22 unknown 03:15–03:45 (good) 89.5° at 09:10 151.5° 2.0

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

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