← 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, 06 September 2028 · astronomical night 21:21 → 05:16 (7.92 h) · Moon 92% (waning gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 21:55–22:05: quality 0.2M33 22:05–22:40: quality 0.3M33 22:40–00:30: quality 0.4M33 00:30–05:20: quality 0.3M33 05:20–05:55: quality 0.2M33 05:55–06:30: quality 0.1observe M33 22:20–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
19:45–22:20 — nothing worth pointing at — 2.58
22:20–05:20 M33 7.0 0.34
05:20–06:55 — nothing worth pointing at — 1.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 25 unknown 22:20–05:20 (marginal) 79.1° at 03:50 21.4° 7.0

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

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