← 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, 28 October 2028 · astronomical night 19:53 → 05:16 (10.37 h) · Moon 82% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 18:55–19:25: quality 0.1M33 19:25–19:55: quality 0.2M33 19:55–23:55: quality 0.5M33 23:55–02:30: quality 0.6M33 02:30–03:55: quality 0.7M33 03:55–03:50: quality 0.9M33 03:50–04:35: quality 0.8M33 04:35–04:50: quality 0.7M33 04:50–05:05: quality 0.6M33 05:05–05:20: quality 0.5M33 05:20–05:25: quality 0.2observe M33 19:55–05:20scheduleM3320: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
18:20–19:55 — nothing worth pointing at — 1.58
19:55–05:20 M33 10.42 0.61
05:20–06:50 — nothing worth pointing at — 1.5

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 91 unknown 01:25–05:00 (good) 79.1° at 00:25 47.7° 10.42

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

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