← 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 Saturday, 29 August 2026 · astronomical night 21:38 → 05:05 (7.44 h) · Moon 97% (waning gibbous) · weather: ERA5 history

NGC 7000NGC 7000 20:30–21:05: quality 0.1NGC 7000 21:05–21:40: quality 0.3NGC 7000 21:40–22:00: quality 0.6NGC 7000 22:00–22:25: quality 0.5NGC 7000 22:25–23:00: quality 0.4observe NGC 7000 21:40–23:00scheduleNGC 700020: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–21:40 — nothing worth pointing at — 1.75
21:40–23:00 NGC 7000 1.33 0.48
23:00–06:45 — nothing worth pointing at — 7.75

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
NGC 7000 North America Nebula 64 13 21:40–23:00 (marginal) 87.2° at 23:50 56.9° 1.33

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

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