← 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 Thursday, 22 October 2026 · astronomical night 20:02 → 06:09 (10.12 h) · Moon 87% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 18:25–19:00: unusableM33 19:00–20:05: poorM33 20:05–02:20: marginalM33 02:20–06:10: goodM33 06:10–06:25: marginalM33 06:25–06:50: poorM33 06:50–07:45: unusableobserve M33 20:05–06:25scheduleM3320: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
18:25–20:05 — nothing worth pointing at — 1.67
20:05–06:25 M33 10.33 0.59
06:25–07:45 — nothing worth pointing at — 1.33

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 91 unknown 02:20–06:10 (good) 79.1° at 00:50 47.7° 10.33

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

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