← 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 Thursday, 13 July 2028 · astronomical night 22:59 → 03:55 (4.94 h) · Moon 59% (waning gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M31M31 00:00–00:10: quality 0.3M31 00:10–00:30: quality 0.4M31 00:30–00:55: quality 0.5M31 00:55–04:00: quality 0.6M31 04:00–04:45: quality 0.3M31 04:45–05:30: quality 0.1observe M31 00:00–04:25scheduleM3122: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–00:00 — nothing worth pointing at — 3.17
00:00–04:25 M31 4.42 0.53
04:25–06:00 — nothing worth pointing at — 1.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 38 unknown 03:05–04:00 (good) 89.7° at 06:35 32.0° 4.42

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

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