← 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 Friday, 12 November 2027 · astronomical night 18:39 → 05:31 (10.86 h) · Moon 98% (full moon) · weather: none — the schedule is astronomy only; overall conditions unknown

M42M42 22:45–23:15: quality 0.2M42 23:15–23:50: quality 0.3M42 23:50–02:25: quality 0.4M42 02:25–05:35: quality 0.5M42 05:35–06:05: quality 0.2M42 06:05–06:10: quality 0.1observe M42 23:30–05:35scheduleM4218: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:00–23:30 — nothing worth pointing at — 6.5
23:30–05:35 M42 6.08 0.44
05:35–07:10 — nothing worth pointing at — 1.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 39 unknown 23:30–05:35 (marginal) 42.9° at 02:30 57.1° 6.08

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

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