details & analysis of one

Inferred Command Chain from Tatmadaw to 17 Light Infantry Battalion on 2007/2/1

Our Analysis indicates that this chain of command existed from 2007/2/1 to 2007/2/1. The command chain was built on inferred time ranges of links between 9 units, based off of 90 claims made by 40 sources.

During this time 0 of the units in this chain were named as perpetrators of 0 incidents,, and 0 units had 0 incidents in their area of operations.

Below the chain is shown, with the time ranges for the relation between each unit in the change to show the larger time range of claims that this specific chain was inferred from.

on this page

First Cited or Cited Start ⓘ

2007/2/1 2007/2/1

Last Cited or Cited End ⓘ

🪖 tatmadaw

┄ 1990/1/1〜1991/1/1

2023/5/19 ┈

🪖 deputy commander-in-chief of defence services

┄ 1990/1/1

2023/5/19 ┈

🪖 tatmadaw-kyi

⟝ 2002/1/1〜2003/1/1

2023/4/8 ┈

🪖 joint chief of staff

┄ 2003/5/1

2023/4/1 ┈

🪖 4 bureau of special operations

┄ 2003/5/1

2023/3/31 ┈

🪖 southeastern regional military command

┄ 2007/2/1

2007/2/1 ┈

🪖 1 military operations command

┄ 2007/2/1

2022/3/24 ┈

🪖 unknown tactical operations command (1 military operations command)

┄ 2006/1/1〜12/31

2022/3/24 ┈

🪖 17 light infantry battalion

Incidents With Named Perpetrators

An incident is a public claim made by a civil society organization, an international organization, a government, or another source that a violation of human rights was perpetrated by the defense and security forces of a country. The Security Force Monitor does not make allegations, but relies on descriptions, categorizations, and allegations from other organizations.

During the time-range of this chain of command, 2007/2/1 to 2007/2/1, 0 incidents occurred where a source directly named a perpetrator and are listed below.

0 incidents which directly name a perpetrator in this chain (page 1 / 1)

Incidents Without a Named Perpetrator

During the time-range of this chain of command 0 incidents occurred in locations which overlapped with sites and/or areas of operations of one or more units in the chain. This includes any incident which one or more units in this chain was directly identified in a source as a perpetrator. Incidents which began before or after the time range of this chain of command are not included in the list below.

0 chains (page 1/1)

Claims & Sources

The sources used to infer time ranges and construct this chain of command are listed below. Each individual relationship may contain multiple claims establishing its existence.

90 claims based off 40 sources (page 1 / 9)

...