← 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, 31 December 2028 · astronomical night 18:40 → 06:08 (11.46 h) · Moon 100% (full moon) · weather: none — the schedule is astronomy only; overall conditions unknown

M42M42 19:30–20:00: quality 0.2M42 20:00–22:55: quality 0.3M42 22:55–02:50: quality 0.2M42 02:50–03:05: quality 0.1observe M42 20:25–21:00schedule18: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
17:00–20:25 — nothing worth pointing at — 3.42
20:25–21:00 M42 0.58 0.3
21:00–07:50 — nothing worth pointing at — 10.83

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 14 unknown 20:25–21:00 (marginal) 42.9° at 23:15 34.9° 0.58

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

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