Amavasya (अमावस्या) dates and timings in Melbourne for 2067
Verified astronomical start and end times for lunar day 30 in Melbourne, shown in Australia/Melbourne.
12 occurrences found. Each end time is exclusive: the next Tithi begins at that instant.
| # | Starts | Ends | Duration | Crosses midnight |
|---|---|---|---|---|
| 1 | 15 Jan 2067, 2:03 am GMT+11 | 15 Jan 2067, 10:17 pm GMT+11 | 20 hr 14 min | No |
| 2 | 13 Feb 2067, 12:32 pm GMT+11 | 14 Feb 2067, 8:57 am GMT+11 | 20 hr 26 min | Yes |
| 3 | 14 Mar 2067, 10:19 pm GMT+11 | 15 Mar 2067, 7:29 pm GMT+11 | 21 hr 10 min | Yes |
| 4 | 13 Apr 2067, 7:01 am GMT+10 | 14 Apr 2067, 5:24 am GMT+10 | 22 hr 23 min | Yes |
| 5 | 12 May 2067, 5:30 pm GMT+10 | 13 May 2067, 5:21 pm GMT+10 | 23 hr 51 min | Yes |
| 6 | 11 Jun 2067, 5:27 am GMT+10 | 12 Jun 2067, 6:41 am GMT+10 | 25 hr 15 min | Yes |
| 7 | 10 Jul 2067, 7:05 pm GMT+10 | 11 Jul 2067, 9:16 pm GMT+10 | 26 hr 11 min | Yes |
| 8 | 9 Aug 2067, 10:08 am GMT+10 | 10 Aug 2067, 12:37 pm GMT+10 | 26 hr 29 min | Yes |
| 9 | 8 Sept 2067, 2:03 am GMT+10 | 9 Sept 2067, 4:09 am GMT+10 | 26 hr 6 min | Yes |
| 10 | 7 Oct 2067, 7:16 pm GMT+11 | 8 Oct 2067, 8:28 pm GMT+11 | 25 hr 12 min | Yes |
| 11 | 6 Nov 2067, 11:18 am GMT+11 | 7 Nov 2067, 11:14 am GMT+11 | 23 hr 56 min | Yes |
| 12 | 6 Dec 2067, 2:33 am GMT+11 | 7 Dec 2067, 1:05 am GMT+11 | 22 hr 32 min | Yes |
How these timings are calculated
BDA calculates the geocentric angular separation of the Moon and Sun and divides the full cycle into 30 equal 12-degree Tithi sectors. UTC boundaries are converted to the timezone resolved from the listed city coordinates.
Scope: These are astronomical Tithi spans only. This page does not choose a festival, Vrat, Parana, or Muhurta date. Those decisions require their separately certified sunrise-prevalence and observance rules.
Browse related Tithi timings
Previous year Next year Sydney Brisbane Perth Adelaide Auckland Delhi
Open the live Panchang Browse the monthly Panchang calendar
General Panchang information. Exact timings depend on location. No personal birth data is used.