← 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, 18 January 2027 · astronomical night 18:56 → 06:06 (11.16 h) · Moon 82% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 17:50–18:25: quality 0.1M33 18:25–19:00: quality 0.2M33 19:00–22:55: quality 0.4M33 22:55–23:45: quality 0.3M33 23:45–00:05: quality 0.2observe M33 19:00–23:25scheduleM3318:0020: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
17:15–19:00 — nothing worth pointing at — 1.75
19:00–23:25 M33 4.42 0.38
23:25–07:45 — nothing worth pointing at — 8.33

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 21 unknown 19:00–23:25 (marginal) 79.1° at 18:05 37.2° 4.42

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

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