← 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 Thursday, 29 July 2027 · astronomical night 22:37 → 04:17 (5.67 h) · Moon 17% (waning crescent) · weather: none — the schedule is astronomy only; overall conditions unknown

M45M45 03:05–03:20: quality 0.4M45 03:20–03:35: quality 0.5M45 03:35–03:50: quality 0.6M45 03:50–04:20: quality 0.7M45 04:20–05:05: quality 0.4M45 05:05–05:45: quality 0.1observe M45 03:05–05:05scheduleM4522: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
20:40–03:05 — nothing worth pointing at — 6.42
03:05–05:05 M45 2.0 0.52
05:05–06:15 — nothing worth pointing at — 1.17

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M45 Seven Sisters 21 unknown 03:40–04:20 (good) 72.5° at 08:40 18.1° 2.0

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

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