Beyeren Armorial
collection highlight from the National Library of the Netherlands
The Beyeren Armorial is a manuscript roll of arms of the early 15th century, containing 1096 hand-colored coats of arms, with annotations in Middle Dutch. It is held by in the National Library of the Netherlands in The Hague (KB), shelf mark 79 K 21.
History
The manuscript was compiled at the court of Holland and was completed on 23 June 1405 by Claes Heynenzoon (c.1345−1414). He was Ruwieren King of Arms, the chief herald of the Netherlands around 1400. He is also the creator of the Gelre (Guelders) Armorial, for which he has also been referred to as the "Gelre Herald".
Contents
The manuscripts is divided into 5 series or chapters
I (fol. 1r–8v, 18r–28v): 337 coats of arms from participants in a tournament in Compiègne, "February 1238" [mccxxxviii]: the indicated date is likely in error (as many of the coats of arms would be anachronistic), perhaps 1278 [mcclxxviii] is intended (the coat of arms of the king of Sicily is that of Anjou, for Charles I, r. 1266–1285); the Luxembourg lion for "Henry of Luxembourg" would then be in reference to Henry VI (1240–1288), father of emperor Henry VII.
II (fol. 28v–35v, 49r–52v): 191 coats of arms from participants in a tournament in Mons; 1310
III (fol. 52v–57v, 36r–48v, 9r–13r): 404 coats of arms from participants in a raid against the Frisians in Kuinre; 1396
IV (fol.
Begin with the source’s own compact description: “Beyeren Armorial” is collection highlight from the National Library of the Netherlands. The dossier treats that line as a proposition to test through Beyeren, Armorial and highlight, not as a finished interpretation.
Why this record matters
The phrase “collection highlight from the National Library of the Netherlands” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Aug 8, 2026. The linked authority identifier is Q3372028. 2 of 2 selected statements include explicit references; 2 carry qualifiers and 0 use preferred rank. The first chronological checks are 1096, 1405, 1345 and 1414.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. 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
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Beyeren Armorial”, its source revision and the description used here.
- Expand the search: follow Beyeren Armorial primary sources, Beyeren Armorial archive and Beyeren 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 “Beyeren Armorial”?
- Which authority defined the place, boundary or structure at the relevant date?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Beyeren Armorial” 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.