History Mughal Empire

Raja Desing Short Rule in Gingee: A Tale of Courage and Defiance (1714)

In 1714, Raja Desing (Tej Singh), a young and fiery leader, took charge of Gingee Fort after his father, Swarup Singh, passed away. His rule lasted just ten months, from January to October 3, 1714, but it was filled with bold actions and a fierce clash with Mughal authorities. With limited records from the Madras archives, we rely on the Tamil ballad, Narayana Pillai’s Chronicle, and the Mack. Mss. to piece together his story. This blog post, written in simple English, explores Desing’s journey to Gingee, his brief rule, and his defiant stand against Nawab Sadatullah Khan.

Raja Desing’s Short Rule in Gingee: A Tale of Courage and Defiance (1714)

Journey from Bundelkhand to Gingee

When news of Swarup Singh’s illness reached his family in Bundelkhand, his son, Raja Desing (Tej Singh), set out with his wife, fifty horsemen, and attendants. They traveled to Bidanur (Bednur) in the Carnatic, where the local Raja was struggling against Maratha attacks. The Raja of Bidanur, aware of Swarup Singh’s role as killedar (fort commander) of Gingee, asked Desing for help. After careful thought, Desing agreed and led his small force against the Marathas, successfully driving them back with skill and bravery.

In gratitude, the Raja of Bidanur gave Desing one lakh of rupees, fine clothes, jewels, and a remarkable horse worth 12,000 rupees. This horse, known for being untamable, calmed at Desing’s approach, allowing him to ride it effortlessly. With these gifts, Desing continued his journey to Gingee, only to learn that his father had died during his travels. Upon arriving, Desing performed Swarup Singh’s funeral rites and took over as killedar of Gingee Fort.

Taking Charge of Gingee Fort

Desing assumed control of Gingee, a key Mughal jagir previously managed by his father. The fort’s officials, loyal to Swarup Singh, offered nazar (tribute) and recognized Desing as the new killedar. However, the Mughal officials, including the diwanath (revenue officer) and vaknavis (record-keeper) Payya Ramakrishna, did not pay the customary nazar, wary of Desing’s fiery temper. They hesitated to challenge him directly, knowing he claimed the fort as his hereditary right.

Months later, Payya Ramakrishna cautiously advised Desing that he needed official approval from the Mughal emperor or Nawab Sadatullah Khan to hold the killedari. Desing, proud and defiant, declared that his father had received Gingee’s miras (hereditary right) from Emperor Alamgir (Aurangzeb). He insisted he needed no one’s permission and refused to seek approval, asserting his authority over the jagir’s taluks. For six months, he ruled unchallenged, but tensions were brewing.

Mughal Orders and Growing Tensions

Nawab Sadatullah Khan, based in Arcot, learned of Swarup Singh’s death but did not immediately act to seize Gingee. Instead, he sent Desing a condolence letter, acknowledging his father’s passing. Meanwhile, Desing governed the jagir, managing its lands and revenues. However, trouble arrived when two Mughal harkars (messengers) brought an imperial farman (decree) to Arcot, addressed to Sadatullah Khan, along with orders for Swarup Singh regarding 70 lakhs of rupees in unpaid revenues.

Sadatullah Khan, aware of Desing’s hot-headed nature, instructed his sheristadar, Lala Todar Mall, to handle the situation delicately. Todar Mall was to present the farman and a takid (urgent order) to Desing, take control of Gingee Fort and its jagir peacefully, and escort Desing to Arcot. Todar Mall arrived at Gingee with fifty horsemen and set up camp near the Venkatarama Swami temple, built by Mutiyal Nayakan. The fort’s Mughal officials, including Payya Ramakrishna, met him and reviewed the farman and inayatnama (letter of favor) from Sadatullah Khan.

Defiance at Gingee: The Confrontation

Payya Ramakrishna informed Desing of Todar Mall’s arrival and the Mughal orders, urging him to meet the sheristadar and negotiate. He assured Desing that Todar Mall and Sadatullah Khan were reasonable and might confirm his killedari if he cooperated. Desing agreed to meet Todar Mall and rode out with his father’s equipage to the Rajas’ cremation ground near Melacheri, then to the Chakraperumal temple by the river, before heading to Todar Mall’s camp.

When Todar Mall approached to greet him, Desing offered a salute but remained on his horse, a gesture Todar Mall found disrespectful. Offended, Todar Mall returned to his tent, and Desing rode back to the fort. The next day, Todar Mall, described as mild-mannered, visited Desing’s court, choosing not to dwell on the “characteristic stupidity of the Bundela.” He formally presented the imperial farman and Sadatullah Khan’s inayatnama. Desing, enraged after having them read aloud, declared he would not surrender his father’s jagir. In a dramatic outburst, he warned that any attempt to seize it would lead to “the rolling of many heads” and threw the documents back at Todar Mall.

Todar Mall calmly retrieved the farman and inayatnama and returned to his camp. The fort’s Mughal officials sought his guidance, and he instructed them to continue their duties as usual, avoiding further escalation. Desing’s defiance set the stage for a confrontation that would define his brief rule, leading to his tragic end on October 3, 1714.

Raja Desing’s ten-month rule was a bold but doomed stand against Mughal authority. His claim to Gingee’s miras, rooted in his father’s grant from Aurangzeb, reflected the Bundela pride and independence that Swarup Singh had also displayed. The Tamil ballad and Narayana Pillai’s Chronicle paint Desing as a courageous figure, taming an untamable horse and repelling Maratha foes, yet his temper and refusal to bow to Mughal orders led to his downfall. The lack of detailed Madras records, unlike those for Swarup Singh, underscores the brevity of his rule and its chaotic end.

Note: This post draws on the Tamil ballad, Narayana Pillai’s Chronicle, and Mack. Mss. for a detailed account of Raja Desing’s ten-month rule in 1714.

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *