Rouse-Boughton baronets of Rouse Lench (1791)
extinct baronetcy

Boughton-Rouse baronetcy, shortly thereafter Rouse-Boughton baronetcy, of Rouse Lench in the County of Worcester, was created on 28 July 1791 in the Baronetage of Great Britain for Charles William Boughton-Rouse, an East India Company employee who became Secretary of the India Board in 1784. He was Member of Parliament for Evesham from 1780 to 1790, and for Bramber from 1796 to 1800.
Originally Charles William Boughton, he had inherited in 1768 from Thomas Philips Rouse, and added Rouse to his surname. He married in 1782 the heiress Catherine Hall, daughter of William Pearce Hall of Downton Hall. In 1794 his brother Sir Edward Boughton, 8th Baronet, of the Boughton baronets of Lawford, died and Rouse-Boughton from that point held the united baronetcies.
The 3rd, 4th and 5th baronets all served as High Sheriff of Shropshire.< The baronetcies remained united, and became extinct in 1963.
Rouse-Boughton baronets, of Rouse Lench (1791)
Sir Charles William Rouse-Boughton, 1st and 9th Baronet (1747–1821)
Sir William Edward Rouse-Boughton, 2nd and 10th Baronet (1788–1856)
Sir Charles Henry Rouse-Boughton, 3rd and 11th Baronet (1825–1906)
Sir William St Andrew Rouse-Boughton, 4th and 12th Baronet (1853–1937)
Sir Edward Hotham Rouse-Boughton, 5th and 13th Baronet (1893–1963), left no male heir.
This brief starts where responsible research should: with the source description of “Rouse-Boughton baronets of Rouse Lench (1791)” as extinct baronetcy. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as extinct baronetcy. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Sep 5, 2026. The linked authority identifier is Q138857839. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1791, 1784, 1780 and 1790.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 “Rouse-Boughton baronets of Rouse Lench (1791)”, its source revision and the description used here.
- Expand the search: follow Rouse-Boughton baronets of Rouse Lench (1791) primary sources, Rouse-Boughton baronets of Rouse Lench (1791) archive and Rouse-Boughton 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 “Rouse-Boughton baronets of Rouse Lench (1791)”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Rouse-Boughton baronets of Rouse Lench (1791)” 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.