Skip to content
● Live
Live Islamic date, local prayer times, and rotating source-attributed wisdom.

Sponsored

Partner offers

5 AH · approximately 627 CE · Madinah, Arabia

Battle of the Trench · Khandaq

غزوة الخندق

غزوۂ خندق

Field atlas · Terrain

Interactive 3D map

Preparing the 3D scene…
Educational geographic reconstruction. Marker positions and terrain are schematic, not surveyed battle coordinates.

Historical maps album

58 local-first records

Historical overview

A schematic reading of the defensive landscape associated with the Battle of the Trench near Madinah. The trench line, dwellings, and camp placements are educational scene elements rather than a surveyed archaeological plan.

Historical context and how to read this record

This record presents Battle of the Trench · Khandaq, dated in the archive as 5 AH · approximately 627 CE and associated with Madinah, Arabia. The date, place, summary, named groups, terrain features, and references shown here come from the bundled or published event record. They provide a concise entry point for study, while the linked source notes remain the place to check what each historical or religious text actually reports. A label in the archive is not, by itself, proof that every chronology, number, or interpretation is agreed across historians.

The timeline on this page is deliberately limited to information attached to the record: its displayed event date and era, its named location, and the geographic markers that the map author normalized for the scene. These map markers are not a minute-by-minute sequence of movements. They do not claim to reconstruct every decision, speech, or formation. Where historians preserve differing accounts, the distinction matters: a conventional date can help readers orient themselves, but a date recorded in a database should not be mistaken for a universally settled day or for a primary-source quotation.

The terrain is a deterministic educational model. A shared height function keeps water, formations, landmarks, and ground visually aligned; the normalized coordinates make the same record render consistently when the optional cloud archive is unavailable. This approach supports comparison of broad relationships—such as a camp in relation to a water feature, a fortified settlement against a highland, or a route beside a valley—without presenting synthetic elevation as archaeological survey data. Lighting, camera angle, and visual scale are choices for legibility, not evidence about the historical scene.

Read the forces and commanders panel as a record of the labels supplied for this map, not as an independently verified census. Estimates in classical narratives can differ because authors preserve separate transmissions, use rounded totals, or describe groups in different ways. This page keeps uncertainty notes attached to the relevant record when they are available. A missing strength estimate means the archive does not make one here; it should not be filled by inference from the size of a marker or from the appearance of the 3D scene.

The source dossier names the references bundled with this event, including Qur’anic passages or classical works where supplied. Numbering, chapter divisions, translations, and pagination can vary by edition, so a careful citation should identify the edition and translator consulted. A source title in the list is a research lead, not a claim that the entire event is established by that work alone. Compare the passages in context, separate a source’s wording from later commentary, and consult qualified scholarship when a question concerns creed, law, or a contested historical conclusion.

For an efficient study sequence, begin with the short overview, note the event date and place, then select each geographic marker in the dual reader. The camera will move to the schematic coordinate while the corresponding source note is brought into view. Next compare the land and water features, read any force labels and their uncertainty notes, and return to the source dossier before drawing conclusions. This order helps distinguish what the archive records, what the visualization illustrates, and what a reader may need to verify in a primary edition. The purpose is source-aware orientation and respectful learning, not a substitute for historical fieldwork or a scholar’s judgment.

Record timeline and tactical markers

  1. Archive date: Not recorded · 5 AH · approximately 627 CE
  2. Recorded setting: Madinah, Arabia
  3. Map feature 1: Excavated defensive trench rendered as a terrain cut
  4. Map feature 2: Madinah-side dwellings
  5. Map feature 3: Approach and siege-side camp markers
  6. Map feature 4: Topography and exact trench route remain schematic
  7. Schematic marker 1: Madinah defenders · Prophet Muhammad (s.a.w.w.) · Traditional reports vary
  8. Schematic marker 2: Confederate siege camp · Coalition leadership in historical accounts · Traditional reports vary

Marker ordering is a reading aid, not a chronological claim about the event.

Forces and commanders

  • Madinah defenders — Prophet Muhammad (s.a.w.w.) (Traditional reports vary)
  • Confederate siege camp — Coalition leadership in historical accounts (Traditional reports vary)

Geography: water and landscape

  • Madinah wells (context marker) (wells)
  • Excavated defensive trench rendered as a terrain cut
  • Madinah-side dwellings
  • Approach and siege-side camp markers
  • Topography and exact trench route remain schematic

Sources

  • Qur’an 33:9–27
  • Sahih al-Bukhari, reports of the Battle of the Trench (numbering varies by edition)
  • Trench geometry and camp positions are illustrative, not an archaeological survey

Continue the source trail

More 3D maps

Sponsored

Partner offers

Optional external offers. Open only when you choose.