← 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 Wednesday, 30 June 2027 · astronomical night 23:09 → 03:40 (4.51 h) · Moon 14% (waning crescent) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 02:25–02:30: quality 0.4M33 02:30–02:45: quality 0.5M33 02:45–03:05: quality 0.6M33 03:05–03:20: quality 0.7M33 03:20–03:45: quality 0.8M33 03:45–04:35: quality 0.4M33 04:35–05:20: quality 0.1observe M33 02:25–04:35scheduleM3322: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:55–02:25 — nothing worth pointing at — 5.5
02:25–04:35 M33 2.17 0.54
04:35–05:55 — nothing worth pointing at — 1.33

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 25 unknown 03:00–03:45 (good) 79.1° at 08:20 25.5° 2.17

💡 API
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2027-06-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"}; an unreadable date → 400 {"error", "code": "invalid_date"}.