← 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 Sunday, 26 November 2028 · astronomical night 18:31 → 05:46 (11.25 h) · Moon 76% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 17:25–18:00: quality 0.1M33 18:00–18:35: quality 0.2M33 18:35–19:00: quality 0.4M33 19:00–19:40: quality 0.5M33 19:40–20:40: quality 0.4M33 20:40–00:55: quality 0.5M33 00:55–02:35: quality 0.6M33 02:35–02:40: quality 0.5M33 02:40–02:45: quality 0.8M33 02:45–02:55: quality 0.7M33 02:55–03:10: quality 0.6M33 03:10–03:25: quality 0.5M33 03:25–03:35: quality 0.4observe M33 18:35–03:35scheduleM3318:0020:0022: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
16:50–18:35 — nothing worth pointing at — 1.75
18:35–03:35 M33 9.0 0.51
03:35–07:25 — nothing worth pointing at — 3.83

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 75 unknown 02:40–03:05 (good) 79.1° at 21:30 29.4° 9.0

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

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