← 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, 31 August 2026 · astronomical night 21:34 → 05:08 (7.56 h) · Moon 85% (waning gibbous) · weather: ERA5 history

M42M42 04:30–04:40: quality 0.2M42 04:40–05:05: quality 0.3M42 05:05–05:10: quality 0.4M42 05:10–05:45: quality 0.2M42 05:45–06:20: quality 0.1observe M42 04:50–05:10schedule20: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
19:55–04:50 — nothing worth pointing at — 8.92
04:50–05:10 M42 0.33 0.33
05:10–06:50 — nothing worth pointing at — 1.67

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 3 3 04:50–05:10 (marginal) 42.9° at 08:15 65.1° 0.33

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

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