← 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, 27 January 2040 · astronomical night 19:05 → 06:01 (10.93 h) · Moon 98% (full moon) · weather: none — the schedule is astronomy only; overall conditions unknown

M31M31 18:00–18:35: quality 0.1M31 18:35–19:10: quality 0.3M31 19:10–19:40: quality 0.7M31 19:40–21:05: quality 0.6M31 21:05–22:25: quality 0.5M31 22:25–22:50: quality 0.4M31 22:50–23:20: quality 0.3observe M31 18:35–23:05scheduleM3118: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:25–18:35 — nothing worth pointing at — 1.17
18:35–23:05 M31 4.5 0.51
23:05–07:40 — nothing worth pointing at — 8.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 41 unknown 19:10–20:20 (good) 89.8° at 16:40 83.5° 4.5

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

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