Shubh Muhurat 2027 Dataset — CSV & JSON Download

The Bela shubh muhurat 2027 dataset contains 1,324 shubh dates across 8 life events, 1 January 2027 to 31 December 2027, computed for Delhi (IST). Download CSV or JSON — every row lists its exact window, tithi, nakshatra, score and rule counts. CC-BY 4.0: reuse freely, cite Bela.

Reference city: Delhi (IST)Ayanamsa: LahiriEngine stamp: 2026-08-06✓ CC-BY 4.0

Download

muhurat-2027.csv · generated at build

Flat rows, one per shubh date × event. Opens in any spreadsheet.

muhurat-2027.json · generated at build

Same columns plus the verbatim per-rule breakdown for every date, and the full column dictionary.

Column dictionary

15 columns in both CSV and JSON
ColumnTypeMeaning
eventstringEvent slug, e.g. vivah, griha-pravesh.
event_namestringHuman-readable event name.
datedate (yyyy-mm-dd)Gregorian date of the muhurat, Delhi (IST) civil calendar.
weekdaystringWeekday in Delhi.
window_startISO 8601 datetimeStart of the best auspicious window, with IST offset.
window_endISO 8601 datetimeEnd of the best auspicious window, with IST offset.
choghadiyastringChoghadiya period of the chosen window (Amrit/Shubh/Labh/Char preferred).
tithistringLunar day (tithi) prevailing at the window.
nakshatrastringNakshatra prevailing at the window.
scoreinteger 0–100Bela timing score: clamp(round((engine_score + 40) × 100 / 95), 0, 100). 70+ auspicious, 40–69 moderate, below 40 avoid.
engine_scoreintegerRaw engine score before the 0–100 mapping (roughly −40…55).
rules_passintegerCount of classical rules passed (Rahu Kaal, choghadiya, Panchaka, nakshatra, tithi, yoga…).
rules_failintegerCount of rules failed on the day's best window.
rules_warnintegerCount of rules at caution (bad-but-not-worst yoga).
rules_infointegerCount of neutral notes (e.g. Abhijit bonus not hit).

Preview — first 12 rows

1,324 rows in the full file
DateEventWindow (IST)TithiNakshatraScoreRules
1 January 2027Business Opening2:07 AM – 3:49 AMDashamiSwati899✓ 0✕
1 January 2027Shubh (General Auspicious Work)2:07 AM – 3:49 AMDashamiSwati899✓ 0✕
1 January 2027Property Purchase2:07 AM – 3:49 AMDashamiSwati899✓ 0✕
1 January 2027Contract Signing (Signing)2:07 AM – 3:49 AMDashamiSwati899✓ 0✕
1 January 2027Travel (Journey)2:07 AM – 3:49 AMDashamiSwati899✓ 0✕
1 January 2027Vehicle Purchase2:07 AM – 3:49 AMDashamiSwati899✓ 0✕
2 January 2027Business Opening2:59 PM – 4:17 PMEkadashiSwati899✓ 0✕
2 January 2027Shubh (General Auspicious Work)2:59 PM – 4:17 PMEkadashiSwati899✓ 0✕
2 January 2027Property Purchase2:59 PM – 4:17 PMEkadashiSwati899✓ 0✕
2 January 2027Contract Signing (Signing)2:59 PM – 4:17 PMEkadashiSwati899✓ 0✕
2 January 2027Travel (Journey)2:59 PM – 4:17 PMEkadashiSwati899✓ 0✕
2 January 2027Vehicle Purchase2:59 PM – 4:17 PMEkadashiSwati899✓ 0✕

License & citation

Released under CC-BY 4.0. Reuse, redistribute and build on the data — commercially or not — with attribution. Suggested citation:

Muhurat dates: Bela (bela.so/datasets/), computed 2026-08-06from the classical panchang for Delhi (IST), Lahiri ayanamsa.

Windows are computed for Delhi and shift with location — say so when you quote them. How dates are chosen: methodology. Browse the same data as ranked pages: muhurat 2027.

Frequently asked questions

What does one row in the muhurat-2027 dataset represent?

One row is one shubh date for one event in 2027: the day's single best choghadiya window that clears Rahu Kaal, Yamaganda, Gulika, Durmuhurtam and bad Panchaka, with a suited nakshatra and a non-rikta tithi. The rules_pass/fail/warn columns summarise the classical breakdown; the JSON file carries that breakdown verbatim for every row.

How do I cite this dataset?

The license is CC-BY 4.0. A citation like "Muhurat dates: Bela (bela.so/datasets/), computed 2026-08-06 from the classical panchang for Delhi (IST)" is enough. Link the dataset page rather than re-hosting where possible — the data is regenerated when the engine or window rolls forward.

Can I filter rows where a specific rule failed?

Yes — use the JSON file: every row has a rules array with name, passed (true/false/"warn"/"info") and a human-readable detail string per classical rule. The CSV keeps only the aggregate counts to stay spreadsheet-friendly.