← 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, 28 September 2026 · astronomical night 20:40 → 05:42 (9.03 h) · Moon 94% (waning gibbous) · weather: ERA5 history

M33M33 19:05–20:30: unusableM33 20:30–22:00: poorM33 22:00–23:00: marginalM33 23:00–01:00: poorM33 01:00–07:20: unusableobserve M33 22:00–23:00scheduleM3320: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:05–22:00 — nothing worth pointing at — 2.92
22:00–23:00 M33 1.0 0.33
23:00–07:20 — nothing worth pointing at — 8.33

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 32 10 22:00–23:00 (marginal) 79.1° at 02:25 14.7° 1.0

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

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