← 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, 27 February 2027 · astronomical night 19:40 → 05:25 (9.75 h) · Moon 53% (last quarter) · weather: none — the schedule is astronomy only; overall conditions unknown

M33M33 18:40–19:10: quality 0.1M33 19:10–19:45: quality 0.4M33 19:45–19:50: quality 0.9M33 19:50–20:40: quality 0.8M33 20:40–20:55: quality 0.7M33 20:55–21:05: quality 0.6M33 21:05–21:20: quality 0.5M33 21:20–21:30: quality 0.4observe M33 19:10–21:30scheduleM3320: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
18:05–19:10 — nothing worth pointing at — 1.08
19:10–21:30 M33 2.33 0.63
21:30–07:00 — nothing worth pointing at — 9.5

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M33 Triangulum Pinwheel 33 unknown 19:45–21:00 (good) 79.1° at 15:30 145.1° 2.33

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

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