← 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, 05 August 2028 · astronomical night 22:24 → 04:30 (6.1 h) · Moon 100% (full moon) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 00:00–00:25: quality 0.3M33 00:25–00:45: quality 0.4M33 00:45–02:20: quality 0.5M33 02:20–04:35: quality 0.6M33 04:35–05:15: quality 0.3M33 05:15–05:50: quality 0.1observe M33 00:10–05:15scheduleM3322: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
20:30–00:10 — nothing worth pointing at — 3.67
00:10–05:15 M33 5.08 0.52
05:15–06:25 — nothing worth pointing at — 1.17

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 44 unknown 03:15–04:35 (good) 79.1° at 05:55 72.8° 5.08

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

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