← 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 Friday, 07 May 2027 · astronomical night 22:16 → 04:18 (6.03 h) · Moon 3% (waxing crescent) · weather: none — the schedule is astronomy only; overall conditions unknown

M31M31 04:25–04:40: quality 0.2M31 04:40–05:05: quality 0.3M31 05:05–05:40: quality 0.1observe M31 05:00–05:05schedule22: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:25–05:00 — nothing worth pointing at — 8.58
05:00–05:05 M31 0.08 0.31
05:05–06:10 — nothing worth pointing at — 1.08

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 2 unknown 05:00–05:05 (marginal) 89.6° at 11:00 46.1° 0.08

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

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