Chand Sadagar
Indian merchant
Chand Sadagar (Assamese: চান্দ সদাগৰ, Bengali: চাঁদ সদাগর) or Chandradhar was a sea merchant of Champaknagar. This merchant has been claimed by both the Assamese and the Bengalis. Medieval Bengali poet Bipradas Pipilai mentioned in his "Manasamangal Kāvya" (or "Manasa Vijay") that merchant ship of Chand Sadagar used to proceed to the sea from ancient Champaknagar after passing through Tribeni, situated at the junction of Saptagram and the confluence of Ganges, Saraswati and Jamuna River of modern-day West Bengal. Narayan Dev in the scriptures gave an account in his Manasamangal about the merchant ship of the trader Chand Saudagar proceeding to the sea from ancient Champaknagar passing through Saptagram and Tribeni, the tri-junction of the Ganges, Saraswati and Jamuna River. In the Padma Puran (Hindu Scripture), account of Chand Bania (Sadagar) is specifically mentioned.
The location of Champaknagar
Assamese version
According to Assamese folklore, Champaknagar is placed in Chaygaon, Kamrup, about 30–40 km from Guwahati, Assam. Champaknagar is still there in Chaygaon area of Kamrup dist in Assam. There are remains of ancient structures and also a statue of Devi Kali there, the structure is also known as Mer ghar. Locals believe that it is that house or place where Behula and Lakhindhar spent the first night after marriage and there Lakhindhar was bitten by a Snake sent my Manasa Devi. To escape from the plight of Ma Manasa, Lakhindhar and Behula escaped to a place called Gokul Medh, 3 km south of Mahasthangarh and 9 km north of Bogra town, 1 km from the Bogra-Rangpur road of modern Bangladesh after Behula's Basarghar or Lakhinder's Medh.
The public source identifies “Chand Sadagar” as indian merchant. This brief keeps that definition visible, then builds a research path around Chand, Sadagar and Indian.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Chand Sadagar”, the useful work is to connect “indian merchant” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 14, 2026. The linked authority identifier is Q5070891. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
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 “Chand Sadagar”, its source revision and the description used here.
- Expand the search: follow Chand Sadagar primary sources, Chand Sadagar archive and Chand 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 “Chand Sadagar”?
- 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 “Chand Sadagar” 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.