
We all know that there are total of 51 Shakti-Peethas, but do you know?
⚜️Not all the Shakti-Peethas are located in India.⚜️
Here are the 12 Shakti-Peethas that are outside India.
🌺1. Hingalaj Shakti-Peeth, Pakistan
Brahmarandhra of Sati fell in Baluchistan province of..


Here the incarnation of Adhya Shakti, who killed Mahishasur, is worshiped. It’s located near Karachi of Pakistan. The eyes of Goddess Sati fell here. The Goddess is worshiped as "Mahisha-Mardhini".

Shakti Devi Sugandha,also considered as Ekjata,is situated in Shikarpur,which is 20km north from Barisal in Bangladesh.The nose of Sati had fallen & here she is in the form of “Sunanda Devi Tara or Ekjata and Tryambak”appears as Bhairav.

This temple of Shakti is located near Pashupatinath Mandir in Kathmandu,Nepal. It is about 1 km east of Pashupatinath temple. Here, the knees of Sati had fallen, she is in the form of Devi Mahashira & Kapali appears as Bhairav.

This Shakti Peeth is in the form of a stone slab near Kailash Mountain, Mansarovar, in Tibet. Here, the right hand of Sati had fallen, she is in the form of Devi Dakshayani (who destroyed Daksha Yajna), and Amar appears as Bhairav.

This Shakti Peeth is in Muktinath, in Nepal, near the bank of river Gandaki. Here, the right cheek of Sati had fallen, she is in the form of Devi Gandaki-Chandi, and Chakrapani appears as Bhairav.

This Shakti Peeth is famous as Sitakunda Chandranath; this Peetha is on the top of Chandra-Nath Hills in Chittagong, Bangladesh. Here,the right arm of Sati had fallen,she is in the form of Devi Bhawani & Chandrashekar appears as Bhairav.

The left thigh of Sati fell in Kalajore, Bourbhag village, Near Jaintia-pur, Sylhet District, in Bangladesh. She is worshiped in the form of Jayanti Shakti, and Kramadeeshwar.

This Shakti Peeth is in Kumari Kunda, Chittagong District, in Bangladesh. Here, the spine of Sati had fallen; she is in the form of Devi Sravani and Nimish as Bhairav.

On Sri-Shail of Jaunpur Village, 3 km northeast of Sylhet town in Bangladesh, the neck of Sati had fallen. Here she is in the form of Goddess Maha-Lakshmi, and Shambaraanand appears as Bhairav.

More from Vibhu Vashisth 🇮🇳
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.