← 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 Monday, 06 July 2026 · astronomical night 23:06 → 03:46 (4.67 h) · Moon 59% (waning gibbous) · weather: ERA5 history

M31M31 00:30–00:40: quality 0.3M31 00:40–01:00: quality 0.4M31 01:00–01:25: quality 0.5M31 01:25–03:50: quality 0.6M31 03:50–04:40: quality 0.3M31 04:40–05:25: quality 0.1observe M31 00:30–04:00observe M31 04:15–04:35scheduleM3122:0000:0002:0004: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:55–00:30 — nothing worth pointing at — 3.58
00:30–04:00 M31 3.5 0.53
04:00–04:15 — nothing worth pointing at — 0.25
04:15–04:35 M31 0.33 0.3
04:35–05:55 — nothing worth pointing at — 1.33

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 34 33 03:05–03:50 (good) 89.7° at 07:05 37.8° 3.83

💡 API
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-07-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"}.