The eight-year Mughal siege of Gingee Fort (1690–1698) is one of the most dramatic episodes in the history of the Deccan wars. Conducted under the command of the celebrated Mughal general Zulfikar Khan, the siege drew in princes, Maratha kings, emperors, and spies, playing out across the rocky hills of Tamil Nadu in a slow, grinding war of attrition, diplomacy, starvation, and intrigue. Historians who write about this siege tend to focus on the grand figures — the wily Rajaram who escaped from Gingee at the last moment, the politically ambitious Zulfikar Khan who prolonged the siege for his own reasons, and the aged Emperor Aurangzeb who grew increasingly suspicious of everyone around him. Yet the siege could not have been sustained without a vast web of lesser officers, men of loyalty and tactical intelligence who ensured that the Mughal machinery did not collapse from within.
One such man was Dalpat Rao, later known as Dalpat Rao Bundela or Rao Dalpat Bundela. A Hindu Rajput of the Bundela clan, he served as one of Zulfikar Khan’s most trusted lieutenants during the siege of Gingee and went on to play roles in subsequent Mughal campaigns in the Deccan. Though he never attained the rank of a great Mughal noble or commanded an entire army, his career offers a window into a world that military historians often overlook — the world of counterintelligence, camp surveillance, political management, and the quiet but essential work of maintaining discipline in an army far from home, stretched thin by years of inconclusive warfare.
This article traces Dalpat Rao’s life and service from his role at Gingee to his final moments on the blood-soaked field at Jajau in 1707, examining what his story reveals about the structure of Mughal military service, the nature of the Deccan campaigns, and the place of Hindu Rajput officers in Aurangzeb’s imperial army.
The Mughal Siege of Gingee Fort: Context and Command Structure
To understand Dalpat Rao’s role, it is necessary to appreciate the sheer complexity of the Mughal siege of Gingee Fort and the command structure that held it together through eight gruelling years.
Gingee Fort, perched on three rocky hills in what is today Villupuram District of Tamil Nadu, was one of the most formidable fortresses in southern India. Known as the “Troy of the East” by European observers, it had served as the capital of the Bijapur governors, the Nayakas of Gingee, and later the Marathas. When Rajaram, the second son of Chhatrapati Shivaji, fled the Mughal advance into Maharashtra in 1689 and took refuge inside Gingee Fort, it instantly transformed into the nerve centre of Maratha resistance in the south. From behind its walls, Rajaram coordinated Maratha raids across the Deccan, maintained diplomatic correspondence with the Tamil Nayakas and European trading powers, and kept the spirit of Maratha independence alive while Sambhaji’s death had left the confederacy in disarray.
Emperor Aurangzeb, then conducting his long and ultimately exhausting personal campaign in the Deccan, despatched Zulfikar Khan, son of the powerful noble Asad Khan, to take Gingee and capture or kill Rajaram. What followed was a siege unlike most — less a conventional military investment and more a prolonged political chess game, in which Zulfikar Khan balanced the demands of the emperor against the realities on the ground, managing a fractious army, keeping watch on rival Mughal factions, and dealing with a Maratha defender who used time and terrain with great skill.
Within this complex command environment, Zulfikar Khan relied on a core of proven, personally loyal officers to handle sensitive tasks that could not be entrusted to the general body of the army. Dalpat Rao was one of these men.
Who Was Dalpat Rao? Background and Rise in Mughal Service
Dalpat Rao belonged to the Bundela Rajput clan, a warrior lineage from the region of Bundelkhand in central India. The Bundelas had a long and complex relationship with the Mughal empire. They had fiercely resisted Mughal authority during the reigns of Akbar and Jahangir, most notably under Bir Singh Deo Bundela, who had assassinated Abul Fazl at the instigation of Prince Salim. But over the course of the seventeenth century, many Bundela chiefs and their kinsmen entered Mughal service and rose to considerable prominence, their martial abilities making them valued officers in imperial armies across the subcontinent.
Dalpat Rao’s precise origins within the Bundela clan are not recorded in the major chronicles, but his designation as “Rao” suggests a background of local chieftaincy or at least significant landholder status. He entered Mughal service in the context of the Deccan campaigns that consumed the last decades of Aurangzeb’s reign, and it was in this theatre that he made his reputation. His religion — he was a Hindu — was not an impediment to advancement in the Mughal military system, which had long depended on Rajput officers for cavalry and garrison duties. Even under the increasingly orthodox Aurangzeb, whose religious policies created tensions across the empire, capable Hindu officers continued to serve, fight, and earn distinction.
What distinguished Dalpat Rao from many of his contemporaries was not simply military bravery but a combination of qualities that made him suitable for delicate, politically sensitive assignments. He was loyal, discreet, and possessed the political intelligence to navigate a court environment charged with suspicion and factional rivalry. These qualities brought him to the attention of Zulfikar Khan, and it was Zulfikar Khan who assigned him what would become the most consequential role of his career.
Prince Kam Baksh and the Intrigues at the Siege Camp
Among the figures who complicated the siege of Gingee from the Mughal side, none was more troublesome than Prince Kam Baksh, the youngest son of Emperor Aurangzeb. Kam Baksh was a man of volatile temperament and considerable ambition, qualities that made him both charming and dangerous. From an early age, he had been regarded as his father’s favourite, indulged to a degree that many at court found dangerous. Aurangzeb, who was deeply conscious of the fratricidal wars that had brought him to the throne — he had fought and defeated his brothers and imprisoned his father Shah Jahan — was simultaneously indulgent toward Kam Baksh and apprehensive about his unreliability.
At Gingee, Kam Baksh was present as part of the Mughal army, nominally under the command of Zulfikar Khan but effectively operating as an independent and disruptive presence in the siege camp. The prince was not a man who accepted subordination easily, and the slow, unglamorous work of a long siege chafed against his restless ambition. He looked at Gingee Fort and saw not just a military objective but a political opportunity. If he could make contact with Rajaram and secure a Maratha alliance, or even enter the fort as a guest of the Maratha king, he would be positioned as a player independent of both his father and his rival brothers. In a succession contest — which every Mughal prince knew was inevitable given Aurangzeb’s advanced age — alliances of all kinds had value.
The prince accordingly entered into secret correspondence with Rajaram inside the fort. The exact content of these letters is not fully preserved in any single chronicle, but their general thrust is clear: Kam Baksh was exploring the possibility of coordination with the Marathas, perhaps offering concessions in exchange for support in the eventual struggle for the throne. From Rajaram’s perspective, any contact that divided Mughal attention and potentially brought a Mughal prince into his orbit was worth pursuing, even if the ultimate political value was uncertain.
Zulfikar Khan became aware of these contacts — through his own intelligence networks, which were extensive — and was alarmed. The situation was extraordinarily delicate. Kam Baksh was the emperor’s son. Accusing him openly of treasonable correspondence with the enemy would require solid evidence and the emperor’s sanction, and Aurangzeb’s mood was unpredictable. Any misstep could rebound fatally on Zulfikar Khan himself. What was needed was not confrontation but quiet, deniable surveillance — a man in the prince’s camp who could watch every movement, intercept every messenger, and prevent any actual defection or entry into the fort without creating a formal incident.
That man was Dalpat Rao.
Dalpat Rao as the Prince’s Shadow: Counterintelligence at Gingee
Zulfikar Khan assigned Dalpat Rao to the prince’s camp with instructions that were simple in outline but extremely demanding in execution: watch Kam Baksh at all times, ensure that no secret messenger could reach him from inside the fort, and guarantee that the prince could not slip away to join the Marathas. Dalpat Rao was, in effect, the general’s eyes inside a potentially hostile environment, operating not as an overt guard — the prince would have resisted that — but as a discreet and ever-present check on his freedom of movement.
The position required qualities beyond mere physical courage. Dalpat Rao had to manage the prince’s suspicions while maintaining the surveillance. He had to command the loyalty of soldiers in the prince’s immediate retinue who might themselves be bribed or suborned by Kam Baksh’s agents. He had to maintain communication with Zulfikar Khan without Kam Baksh’s people becoming aware of the reporting channel. And he had to do all of this in a camp environment where relationships were intensely personal, gossip moved at extraordinary speed, and any hint of disloyalty toward the prince could bring swift and violent retribution from Kam Baksh’s own followers.
The siege camp at Gingee was in many respects a world unto itself — a large, semi-permanent military settlement that had grown up around the base of the three hills, housing thousands of soldiers, servants, camp followers, merchants, and hangers-on. Moving through this environment, maintaining contact between the different sections of the camp, tracking who was sending messages and who was receiving them, required both a well-developed network of informants and the personal presence of a man who could read the political atmosphere instantly and act accordingly.
Dalpat Rao’s surveillance proved effective. The correspondence between Kam Baksh and Rajaram did not produce the result either party hoped for. The prince was never able to make direct contact with the fort in a way that could have led to a defection. Rajaram’s own attention was divided between holding Gingee and managing the larger Maratha resistance across the Deccan. And when Rajaram finally escaped from Gingee — slipping out of the fort in disguise and making his way to Maharashtra in 1698, the year the fort fell — he departed without having converted the prince’s overtures into any lasting political arrangement.
The fall of Gingee to Zulfikar Khan in 1698 ended one chapter of Dalpat Rao’s service but by no means his career.
The Broader Significance: Espionage and Camp Discipline in Mughal Deccan Warfare
Dalpat Rao’s role at Gingee illuminates aspects of Mughal warfare in the Deccan that rarely receive the attention they deserve. Modern accounts of the Deccan campaigns tend to emphasize pitched battles, fortification engineering, artillery, and the grand strategic movements of armies. Yet the day-to-day reality of the long Deccan sieges was very different. The armies that conducted these sieges were vast, heterogeneous, and extremely difficult to manage. They were drawn from across the empire — Rajputs from the north, Marathas who had switched sides, Afghan cavalry, Deccani infantry, along with enormous trains of artillery, logistics support, camp followers, merchants, and the families of senior officers. Holding such a force together in the field for years at a time required not just military authority but political management of a high order.
Desertion was a constant problem. The Deccan was harsh, disease was endemic, and the monsoon seasons made movement and supply extremely difficult. Soldiers who had been away from their home regions for years grew homesick and resentful. Famine conditions periodically struck both the besieging army and the surrounding countryside, and food shortages created the conditions for both mutiny and corruption. In this environment, the ability to maintain intelligence about the mood of the camp, to identify potential defectors before they acted, and to manage the relationships between rival factions within the army was as important as any tactical skill.
Dalpat Rao embodied this kind of officer. His service at Gingee was essentially a counterintelligence operation conducted within the army’s own structure — watching not the enemy but a potentially rebellious element inside the Mughal camp itself. His success in this role, maintaining Prince Kam Baksh’s isolation from the Marathas without triggering a formal confrontation, reflects a sophisticated understanding of the political dynamics of the siege.
This dimension of Mughal military history — the espionage, the camp politics, the management of factional conflict within the imperial armies — was first seriously explored by the historian William Irvine in his monumental work The Later Mughals, which drew on Persian chronicles and other primary sources to reconstruct the internal world of the late Mughal military. Irvine’s accounts of figures like Dalpat Rao are invaluable precisely because they rescue from obscurity the middle-rank officers whose careers illuminate the machinery of imperial war.
The Siege of Wagingera: Dalpat Rao in the Last Campaign of Aurangzeb
After Gingee, Dalpat Rao continued in Mughal service through the final years of Aurangzeb’s reign. The aged emperor, now in his eighties, remained in the Deccan, personally directing campaigns that even his most devoted supporters privately recognised as strategically futile. Aurangzeb was pursuing a war that could not be won by the methods he was employing, attempting to extinguish the Maratha resistance through a combination of fortification capture and personal presence — when the resistance had long since ceased to depend on any single fort or capital.
In this context, Dalpat Rao appears in connection with the Siege of Wagingera, described in some accounts as the last major campaign personally supervised by the emperor. Wagingera was a fortified position in the Deccan held by forces aligned with the Bidars — the local powers who had been drawn into the swirling conflict of the period. The Mughal reduction of Wagingera was a step-by-step operation, methodically taking ground position by position around the area of Talwargera, and Dalpat Rao is recorded as playing an active role in seizing key positions during this reduction.
The significance of his appearance at Wagingera lies in what it tells us about his trajectory in Mughal service. He had risen from the covert, political role at Gingee to a more conventionally military one in later campaigns, reflecting the breadth of his abilities. He was not merely a spy-master or political manager but a capable field officer who could take and hold ground under combat conditions.
Aurangzeb’s Death and the War of Succession: Choosing a Side
Emperor Aurangzeb died in March 1707 at Ahmednagar in the Deccan. His death, long anticipated and much dreaded by those who had watched the empire strain under the weight of endless war, triggered the succession conflict that many had seen coming for decades. The Mughal system had no formal mechanism for orderly succession — the throne went to whoever could seize it, and the history of the dynasty was littered with the corpses of princes who had guessed wrong about which brother to support.
Three sons survived Aurangzeb with serious claims: Muazzam, the eldest surviving son, who was stationed in the northwest; Muhammad Azam Shah, the second son, who was in the Deccan with most of the imperial army; and Kam Baksh — the same prince whom Dalpat Rao had watched so closely at Gingee — who was in the south with a following of his own.
The political situation was complex. Muazzam had spent years in disgrace and later in favour, cycling through Aurangzeb’s unpredictable emotional responses to his sons. Azam Shah had the advantage of proximity to the main body of the Deccan army and presented himself as the legitimate heir based on seniority among the surviving princes. Kam Baksh, characteristically, launched his own bid in the south, proclaiming himself emperor and gathering what support he could from the Deccan nobility.
Dalpat Rao Bundela aligned himself with Muhammad Azam Shah. This choice is historically interesting given his earlier role as the agent who had checked Kam Baksh’s intrigues at Gingee — there was presumably no great warmth between Dalpat Rao and the prince he had surveilled for years. But beyond personal factors, supporting Azam Shah reflected a rational calculation. Azam had control of much of the Deccan army, had the strongest claim by traditional succession norms, and had the support of a significant portion of the nobility who had served under Aurangzeb in the south.
Dalpat Rao was listed among Azam Shah’s senior commanders as the army marched north to confront Muazzam’s forces in the climactic battle that would decide the succession.
The Battle of Jajau (June 1707): Death of a Loyal Officer
The Battle of Jajau was fought in June 1707 near the town of Jajau in the Agra region, where the forces of Muhammad Azam Shah met those of Muazzam, who had by then proclaimed himself Emperor Bahadur Shah I. It was one of the decisive engagements of the late Mughal period — a brutal, hard-fought battle that effectively ended Azam Shah’s bid for the throne and set the trajectory of the empire for the next generation.
Azam Shah’s army fought with considerable determination but was ultimately outgeneralled. Muazzam, who had years of experience in the northwest fighting the Sikhs and managing tribal confederacies, proved the more capable commander on the day, and his forces broke Azam Shah’s army in a defeat that was as complete as it was consequential. Muhammad Azam Shah himself was killed in the battle.
Dalpat Rao Bundela died on the same field. The manner of his death is recorded with unusual specificity in the sources — William Irvine’s Later Mughals and related accounts note that he was struck by a swivel-gun ball that entered beneath his chin and exited through his back, a wound that would have been instantly fatal. His body was subsequently recovered for cremation, in accordance with Hindu practice, an act that his companions evidently made the effort to perform even in the chaos of a lost battle.
The specificity of this account — the exact trajectory of the fatal ball, the recovery of the body — suggests that Dalpat Rao’s death was noted and recorded by contemporaries who considered him significant enough to memorialize in this way. In the larger rout of Azam Shah’s forces, when hundreds or thousands of men were dying, the fact that someone took the trouble to record precisely how Dalpat Rao died is a small but meaningful testimony to the regard in which he was held.
Dalpat Rao Bundela in the History of Gingee Fort: Legacy and Significance
Dalpat Rao’s connection to Gingee Fort is one thread in the extraordinarily complex tapestry of the siege of 1690–1698, one of the most significant events in the fort’s long history. For those interested in Gingee’s past, his story offers several important perspectives.
First, it demonstrates the multi-layered nature of the Mughal war effort at Gingee. The siege was not simply a military operation — it was a political operation conducted simultaneously on multiple fronts, with the Mughal command managing not only the Marathas inside the fort but rival factions within its own army. The watch kept on Prince Kam Baksh was in some ways as important as any artillery battery trained on the fort’s walls, because a defection by an imperial prince to the Marathas would have transformed the political situation in ways that military operations alone could not have reversed.
Second, Dalpat Rao’s career illustrates the role of Hindu Rajput officers in the late Mughal military. Despite the religious tensions of Aurangzeb’s reign, the empire continued to depend heavily on the military service of Hindu clans, and men like Dalpat Rao found both space and opportunity within the system. His loyalty was to his commander, Zulfikar Khan, and through him to the imperial cause — a loyalty that survived the end of the Gingee siege and continued through the Wagingera campaign to the final battle at Jajau.
Third, his story is a reminder that the history of any great fortress is not only the history of its defenders but also the history of those who besieged it — the men on the other side of the walls who spent years of their lives in the effort to bring it down, who suffered the same diseases and shortages and homesickness as the garrison, and who brought their own ambitions, loyalties, and personal stories to the long drama of the siege.
Dalpat Rao Bundela was one such man — a loyal officer in a difficult campaign, a counterintelligence operative in a politically explosive situation, a field commander in the last of Aurangzeb’s wars, and finally a casualty on the losing side of an imperial succession struggle. His name deserves to be remembered alongside the more celebrated figures of the Gingee siege, as a representative of the many capable, dedicated men whose careers were shaped by this remarkable fortress and its eight-year resistance.
Recent Posts
- The French Capture of Gingee: September 1750
- Military Movements in Carnatic and Gingee : Summer 1750
- The Battle of Ambur: Nawab Anwaru’d-din Khan’s Biography and the Carnatic Succession Crisis
- Death of Asaf Jah and the Carnatic Succession Crisis of 1748
- Administrative Changes and Turmoil at Gingee in the 1740s
- Nizam’s Intervention in the Carnatic (1743): Power, Intrigue, and Tragedy
- Safdar Ali Khan: Rule, Intrigue, and Assassination in the Carnatic
- Carnatic Politics 1734–1750: A Tumultuous Era of Intrigue and Conquest