← 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 Wednesday, 26 August 2026 · astronomical night 21:44 → 05:01 (7.27 h) · Moon 98% (full moon) · weather: ERA5 history

M33M33 22:40–22:45: quality 0.2M33 22:45–23:05: quality 0.3M33 23:05–23:30: quality 0.4M33 23:30–00:35: quality 0.5M33 00:35–02:15: quality 0.6M33 02:15–03:00: quality 0.7M33 03:00–03:30: quality 0.6M33 03:30–05:05: quality 0.7M33 05:05–05:35: quality 0.4M33 05:35–05:40: quality 0.5M33 05:40–06:00: quality 0.1M33 06:00–06:15: quality 0.2observe M33 22:55–05:40scheduleM3322: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
20:00–22:55 — nothing worth pointing at — 2.92
22:55–05:40 M33 6.75 0.58
05:40–06:45 — nothing worth pointing at — 1.08

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 74 72 01:25–05:05 (good) 79.1° at 04:35 75.4° 6.75

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

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