← 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 Sunday, 06 September 2026 · astronomical night 21:22 → 05:16 (7.89 h) · Moon 22% (waning crescent) · weather: ERA5 history

NGC 7000NGC 7000 19:45–20:15: unusableNGC 7000 20:15–20:50: poorNGC 7000 20:50–21:25: marginalNGC 7000 21:25–05:20: goodNGC 7000 05:20–05:35: marginalNGC 7000 05:35–06:10: poorNGC 7000 06:10–06:55: unusableobserve NGC 7000 20:50–05:35scheduleNGC 700020:0022:0000:0002:0004:0006:00

Faded bands: each target's own windows (green good, amber marginal, pink poor). Dark blue: the schedule. Grey columns: twilight.

Schedule

localtargethoursmean quality
19:45–20:50 — nothing worth pointing at — 1.08
20:50–05:35 NGC 7000 8.75 0.89
05:35–06:55 — nothing worth pointing at — 1.33

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
NGC 7000 North America Nebula 100 99 21:25–05:20 (good) 87.2° at 23:15 106.9° 8.75

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