← 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 Tuesday, 24 October 2028 · astronomical night 19:58 → 06:11 (10.22 h) · Moon 47% (first quarter) · weather: none — the schedule is astronomy only; overall conditions unknown

M31M31 18:55–19:30: quality 0.1M31 19:30–20:00: quality 0.4M31 20:00–20:50: quality 0.8M31 20:50–23:50: quality 0.9M31 23:50–03:15: quality 1.0M31 03:15–04:40: quality 0.9M31 04:40–05:35: quality 0.8M31 05:35–05:50: quality 0.7M31 05:50–06:05: quality 0.6M31 06:05–06:15: quality 0.5M31 06:15–06:30: quality 0.2observe M31 19:30–06:15scheduleM3120: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
18:25–19:30 — nothing worth pointing at — 1.08
19:30–06:15 M31 10.75 0.87
06:15–07:50 — nothing worth pointing at — 1.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M31 Andromeda Galaxy 100 unknown 20:00–06:00 (good) 89.7° at 23:50 88.6° 10.75

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

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