Rani Yan Yan
rani of Chakma Circle

Rani Yan Yan (born 1984) is an Indigenous human rights defender and women's rights activist from Bangladesh, serving as the advisor to the Chakma Circle Chief. In 2014, she married Devasish Roy, the Chakma Circle Chief, and has since been known as Rani Yan Yan.
Career
As the Chakma Rani (queen) and advisor to the Chakma Circle Chief, she has effectively advocated for the appointment of more women as headmen and karbaris (traditional leaders), ensuring women's rights are upheld within the traditional system.
She has advised organizations on climate resiliency and gender equality, researched political participation of Indigenous women, and mentored youth activists on diversity and social inclusion.
In 2018, while supporting two Indigenous teenage girls who had been sexually assaulted, Rani Yan Yan was attacked.
During the COVID-19 pandemic, she promoted simple, low-cost water supply systems to encourage handwashing in remote Indigenous communities, addressing health and food security challenges.
In recognition of her efforts, Rani Yan Yan was honored with the Global Anti-Racism Champions Award by the U.S. Department of State in 2023.
On 6 April 2026, the Rangamati District Magistrate, on the directive of the Ministry of Home Affairs, issued a formal caution to Yan Yan, accusing her of spreading "false and misleading information" against the Bangladeshi government and military. Yan Yan's lawyers denied the accusations and requested the caution be withdrawn. The human rights organisation Front Line Defenders described the caution as being "directly connected" to Yan Yan's human rights activism.
“Rani Yan Yan” enters the record as rani of Chakma Circle. Crown Archives preserves that source wording while asking what Rani, rani and Chakma can confirm, complicate or overturn.
Why this record matters
“Rani Yan Yan” is worth following because a concise public description often conceals a longer documentary argument. Here, Rani, rani and Chakma provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 11, 2026. The linked authority identifier is Q133064816. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1984, 2014, 2018 and 2023.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Rani Yan Yan”, its source revision and the description used here.
- Expand the search: follow Rani Yan Yan primary sources, Rani Yan Yan archive and Rani research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Rani Yan Yan”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Rani Yan Yan” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.