The D'Arcy Archive
One record set, every spelling · 16 September 2026

Every Spelling of One Name

373 index entries under 20 spellings of one surname — and the rarest of them is the one this family used.

27 spellings of this surname have been put to one record set — FindMyPast's England Births & Baptisms 1538-1975 — searched nationally, every form asked the same way, every entry of every productive form read. 20 return something. Together they hold 373 index entries between 1565 and 1909, and the shape they make is not the shape this archive had assumed. Index entries are not children: the five largest forms have now been counted one by one, and the difference is about one entry in six. The measurement is below.

One record set, one county mostly, one index. The set is the FamilySearch transcription of English parish registers and bishops' transcripts, and it is neither complete nor free of duplication — this page counts index entries, not children, and the Entries column is headed that way on purpose. Its value here is that it names the father's first name for almost every entry, and that the same query can be run twenty-seven times with only the surname changed. That makes it a measuring instrument for spellings, which is a different job from finding a person.
The measurement

28 strings put to one index

SpellingEntriesWhere they areFirstLast
SANIGER 158 Berkeley (115), Thornbury, Bristol, Stone, Tidenham, Dursley, St Botolph Aldgate
SANIGAR 56 Thornbury, Berkeley, Bristol, Dursley, St Botolph Aldgate — and the register reading of the 1828 Bristol marriage this archive had published as SANIGRE
SAINGER 30 Berkeley (26), and four strays
SINEGAR 28 Dursley, Cam, Southwell (Notts), Bristol, Purton (Wilts)
SINNEGAR 26 Cam, Dursley, Alderley, Granby cum Sutton (Notts)
SYNAGER 10 Mortlake, Surrey (9); Elmore, Glos (1)
SANNIGER 10 Dursley, Berkeley, North Nibley, Stinchcombe, Frampton, Thornbury, Birmingham
SANEGER 8 added 21 September
SANEGAR 7 Stinchcombe, King's Stanley, Cam, North Nibley, Westminster, Bristol
SINIGER 7 added 21 September
SINEGER 6 added 21 September
SINNEGER 5 Cam (4); Mortlake (1)
SYNIGAR 5 King's Stanley (4); Stroud (1)
SANIGOR 4 Berkeley (3); Upton Warren, Worcs (1)
SANNEGAR 4 added 21 September
SANIGEAR 3 added 21 September
SINIGAR 2 added 21 September
SINNIGER 2 Slimbridge 1629; Dursley 1720, father Abraham — found by wildcard, 21 Sep
SINAGER 1 Bristol
SANNIGAR 1 added 21 September
SINIGOR 0 nought here — one Stinchcombe marriage of 1801 (21 Sep)
SANIGRE 0 nought in this set — and the INDEXED form of Thomas’s 1828 marriage; the register itself reads SANIGAR (22 Sep)
SANYGER 0 the 1608 muster only
SYNIGER 0 the 1608 muster only
SYNEGAR 0 nothing
SANIGAER 0 nothing
SENIGAR 0 nothing
LINEGAR 0 not a spelling — an S read as an L by a GRO indexer; it carries Thomas's 1871 marriage (27 Sep) 1871 1871

20 spellings returned entries; 8 returned none. Every entry of every spelling was read. The column counts index entries, not children — see What this page is not, and by how much below for how far the two diverge.

Recounted

A note on the number, which has moved twice and changed unit once

This page first reported 340 baptisms across fifteen spellings, twelve of them productive, on 17 September. That was accurate for the fifteen forms then tried. On 21 September the remaining forms from this archive's own spelling table were put through the same query, bringing it to 24 tried and 371 entries. The basis did not change and neither did any earlier count — SANIGER is still 158, SANIGOR still 4. Only the number of questions asked changed, which is the only honest reason a total should move.

Later the same day the word changed. The table said baptisms where it had counted entries, and the difference is about one in six. The counts are untouched; the noun is corrected, and the measurement behind the correction is set out below. A 25th form was added at the same time — SANIGRE, which returns nothing here and everything that mattered elsewhere.

And it moved a third time the same evening, which is the point. A single wildcard query over eleven years of one county turned up SINIGOR and SINNIGER, neither of them in the table that had just been called complete. SINNIGER is productive: two baptisms, one of them Abraham's son at Dursley in 1720. 25 became 27 and 371 became 373, and the number is a floor.

Two forms deliberately left out. SINGER and SANGER. They are in this archive's alias list and they return 127 and 40 in Gloucestershire alone — because they are ordinary English surnames in their own right, not forms of this one. Counting them would drown the table in strangers, which is the opposite of what it is for.
What the table says

Five things, in order of how much they cost

The rarest spelling of all is the one this family used. SANIGOR returns four entries in four hundred and thirty-seven years. One is Hannah, baptised at Berkeley on 18 August 1804, father Jno. Two more are her family's, Berkeley 1690 and 1691, father Edward. The fourth is a Worcestershire stray. Against 158 SANIGERs and 56 SANIGARs, that is one entry in eighty-five. This archive searched for her twice and declared her missing twice, and the reason is on this table: the form the Berkeley clerk used for her is the one no alias list would think to carry. documented
A forty-four-year hole that was never a hole. Read alone, SANIGER at Berkeley has a gap from 1632 to 1676 — forty-four years in which the surname appears not once, which any honest reading would put down to the Civil War and the Commonwealth registers. It is not a gap. SAINGER supplies twenty-six Berkeley baptisms between 1655 and 1694, and SANIGOR two more in 1690 and 1691, all of them inside it. For four decades the Berkeley clerk simply wrote the name a different way, and the modern index faithfully preserved his habit as a silence. documented
Two spellings, two places, eight miles apart. The forms split cleanly, and the split is geographic. The -ANIG- family — SANIGER, SANIGAR, SAINGER, SANIGOR, SANNIGER — belongs to the Severn Vale: Berkeley, Thornbury, Stone, Slimbridge, Frampton. The -INEG- family — SINEGAR, SINNEGAR, SINNEGER, SINNIGER — belongs to the Cotswold scarp above it: Dursley, Cam, Stinchcombe, North Nibley, Alderley. Each has its own patriarchs. In the Vale they are Edward, William and Morgan; on the scarp they are Abraham at Dursley from 1698 and Daniel at Cam from 1729, and the two sets of names barely touch. The oldest entries of all, SYNIGAR at King's Stanley in 1591-96 to a William, sit further up the same scarp — and King's Stanley is one of the places the 1608 muster puts this surname. inferred
And Hannah's family crossed the line. She was baptised SANIGOR at Berkeley, a Vale spelling in a Vale parish. By 1841 she is keeping house in Bristol as SINEGAR with a seventy-year-old Lyddya Sinegar, and her brother is Thomas Sinegar of St Philip and Jacob, whose children are indexed here as Lydia Sanigar 1831, Ada Sinager 1855 and John Sinegar 1860. One family, four spellings, in one city, inside thirty years. Whatever kept the two forms apart in the countryside did not survive the move. documented
Two groups that are probably not this name at all. Mortlake, Surrey holds nine of the ten SYNAGERs and one SINNEGER between 1668 and 1718 — a self-contained family two counties away with no Gloucestershire connection on any record here. And Whitechapel in 1845 and 1847 has Peter and Johannes Christian Sainger, sons of Cornelius: those are German given names, and SÄNGER is an ordinary German surname. Counting either group into this family would inflate it with strangers. disputed
The second family · 20 September 2026

The other family, on the scarp

The spelling sweep turned up a second group this archive had never written about, and it is not a footnote: the -INEG- forms belong to their own parishes and their own patriarchs, eight miles east of Berkeley and up the hill. They are set out here because leaving them in a table was how they stayed invisible.

PatriarchParishChildren in the indexSpelling
ABRAHAMDursley Jno 1698 · Will 1701 · Jane 1707 · Thomas 1712 · Thomas 1720SINEGAR / SINNEGAR / SINNIGER
DANIELCam Danll. 1729 · Deborah 1730 · Katherine 1738 · Willm. 1741 · George 1744 · Solomon 1745 · Solomon 1747 · Ann 1752 · Mary 1755 · Henry 1757 · Sarah 1760 · Betty 1749SINNEGAR / SINEGAR / SANEGAR
JOHNCam John 1677 · Rich. 1677 · Daniel 1679 · John 1680SINNEGER
THOMASCam Betty 1770 · Thomas 1773 · Daniel 1775 · Deborah 1780 · Thos. 1783 · Deborah 1788 · Mary 1778SINNEGAR / SINEGAR
BENJAMINStinchcombe & North Nibley Hester 1732 · Richd 1739 · Sara 1719 · Sarah 1723 · Mary 1726SINEGAR / SANNIGER / SANEGAR
WILLIAMKing's Stanley Jane 1591 · Mary 1592 · Rich 1594 · Walter 1596SYNIGAR

documented

Why it matters to this archive and not only to that one. Hannah Saniger was baptised SANIGOR at Berkeley, a Vale form in a Vale parish, and by 1841 she was keeping house in Bristol as SINEGAR — a scarp form. Her brother is Thomas Sinegar of St Philip and Jacob. Whoever was writing their surname in Bristol was using the other family's spelling, and until this sweep this archive had no idea there was another family to borrow it from.
Two Solomons, two Deborahs, and what that means. Daniel of Cam baptised a Solomon in 1745 and another in 1747, and Thomas of Cam a Deborah in 1780 and another in 1788. Repeating a name is what a family did when the first child died, so each pair is almost certainly a burial this archive has not looked for. Daniel's twelve entries across thirty-one years are the largest single sibling group the surname produces anywhere, in either spelling family. inferred
Whether they are one family with the Vale. Not answered, and a baptism index cannot answer it. The Vale patriarchs are Edward, William, Maurice and Morgan; the scarp's are Abraham, Daniel, John, Thomas and Benjamin, and the two sets of forenames barely overlap. The oldest entries of all — SYNIGAR at King's Stanley in 1591–96 — sit further up the same scarp, and King's Stanley is one of the places the 1608 muster puts this surname. That is the only thread joining the two, and it is a place-name, not a person. not claimed
Limits

What this page is not, and by how much

It is not a count of people, and it is not a count of baptisms. The index repeats itself. On 21 September the five largest forms were read row by row and counted as events rather than as rows. The table below is that count; the figures under it are derived from it, not typed.

The repetition is not spread evenly, and that is the useful part. It sits almost entirely in SANIGER and SANIGAR, the two forms in which the Berkeley and Bristol registers were transcribed more than once. SINNEGAR repeats not at all. Duplication tracks the transcription, not the name — so a form's entry count says as much about how often its parish was typed up as about how often the name was written. Mary, daughter of Samuell, is indexed four times in 1688; Sarah, daughter of William, four times at Bristol in 1839.

This page reported earlier that 33 of the 158 SANIGER entries were duplicates, leaving 125. That count is confirmed and refined, not overturned: 125 is right if the father's name is read as a string, and 121 once Edw and Edward, Wm and William, Jos and Joseph are read as the same man, which they plainly are.

SpellingIndex entriesBaptismsRepeats
SANIGER158 12137
SANIGAR56 4511
SAINGER30 291
SINEGAR28 271
SINNEGAR26 260
Counted298 24850

298 index entries are 246 baptisms — 50 repeats within a spelling, and 2 more baptisms that appear under two spellings each: Morris son of Morris at Berkeley in 1677, and William son of William at Bristol in 1830. That is one entry in 6. The remaining 75 entries across 23 smaller forms have not been counted this way.

And part of the duplication has an explanation now. England Births & Baptisms 1538-1975 is not purely Anglican: it ingests the RG 4 non-conformist registers as well. Rose Sanigar, baptised at Dursley in 1781, is in this table twice — and she is also one of eight SANIGAR entries in the separate non-conformist set, all of them at Dursley, Corn Meeting, Congregational. So some of the repeats counted above are not one register typed up twice but one register reaching the index by two routes, which is a better account of them than «transcribed more than once» and does not change the count.
The better instrument

One query that would have done the work of twenty-five

This whole table is a list of guesses about how a clerk might have spelled a name, and the site it was measured on does not need the guesses. The surname box takes wildcards. `SNG*` asked of Gloucestershire marriages for the three years 1827-1829 returns 53 rows, and in them:

Thomas Sanigre, 1828, Martha, Bristol — the marriage this archive searched for under eight spellings and recorded as not existing. And John Saniger, 1827, Ann, Rodborough standing beside John Sanigor, 1827, Ann, Rodborough — one wedding indexed under two forms, one of them the rare spelling that had already hidden Hannah's baptism for two searches.

It is not a free win. The same 53 rows hold Sanger, Shearing and Sheering, and the same pattern run nationally across the whole baptism set would return hundreds of strangers. The wildcard buys completeness and spends it on noise, so it works where a question has a place and a decade and fails where it has neither. That is the opposite trade from this table, which asks twenty-five narrow questions across four centuries. Both are worth having; this archive had only one of them.

And it found two spellings this table did not have. The same 122 rows hold SINIGOR — Sarah, Stinchcombe, 1801 — and SINNIGER, the same marriage indexed a second way. Put back to the baptism set on the table's own basis, SINNIGER returns two: Margrett at Slimbridge in 1629 and Thomas, son of Abraham, at Dursley in 1720 — Abraham being the scarp patriarch this page already names. SINIGOR returns nought, like SANIGRE. Eleven years of one county, one query, two forms missing from a table that had just been rebuilt and called complete. Both are in it now, and the honest reading is that this table is a floor and not a ceiling.

And the trade is not the same for every surname, which is worth saying before anyone takes this away as a rule. The Defranceski session ran the same method on an Italian surname the same afternoon: the exact spelling returns 5 in the England and Wales indexes, and the wildcard `DEFRANC` returns 608 — almost all of them de France, de Franca, Barker or Defrance*, a Huguenot-derived English surname with no connection to theirs. Their signal was in the exact five, and it would not have been easier to see among six hundred.

The variable is whether the stem is native to the archive's language. Snig- is rare in England, so the noise here stays readable: 122 rows for eleven years of one county, six of them this family. Defranc- in England is everywhere. The method is the same and the arithmetic is not, so the honest form of the rule is: use the wildcard where the stem is foreign to the records, and use it inside a narrow window in any case.

And there is a way to know which case you are in, which costs one query. The rule as first written here — use the wildcard where the stem is foreign to the records — asks the searcher to judge something they usually cannot. Measure it instead. Run the exact spelling first, then the wildcard, and read the ratio. Here, `SNG` over eleven years of one county returns 122 rows of which six are this family: one in twenty, and the other nineteen are legible in the result set and can be discarded by reading. The Defranceski archive's is one in a hundred and twenty, because Defranc-* is a native English stem and theirs is not an English family.

The governing variable is the rarity of the thing sought in the corpus it is sought in, and the instrument does not know that number. Neither does a spelling list. The difference is that the wildcard can be made to report it, for the price of one extra search, before anything is built on what comes back.

documented

What this table is a table of

One of these rows is a register and the rest are an index

Every count in this table is of index entries, and an index entry is somebody's reading of a register. On 22 September Bristol Archives read one of the underlying registers and disagreed with the index about the spelling: the entry this table credits to SANIGRE is written SANIGAR in the book.

That is one row of hundreds, and there is no reason to think it is the only one. A surname with this many forms generates them at two stages — the clerk's ear in 1828, and the transcriber's eye in about 1990 — and a table built from an index can only ever see the second. It is still the right table to search from. It is not a table of how anybody spelt their name. [Own error 43](/corrections/).

the disagreement is documented; neither spelling is

The blind spot

And one row in this table does not begin with an S

Every search this archive has run on this surname has assumed the first letter. The wildcard is `SNG*`; the phonetic code is S526. Both are blind in the same place.

Thomas Sinegar's marriage of 28 May 1871 is in the GRO index as THOMAS LINEGAR. It was found only by asking for the bride instead — Julia Marsh, Bristol 6a 131 — and reading the men off the page. No S-form query of any kind reaches it, and it would have gone on being a null.

This is not a spelling and it is in the table anyway, at nought, because the table's job is to make records findable and this is how one record is filed. It also means that every null this archive has recorded against a wildcard or a phonetic search on this name is a null about the S forms, not about the family. The L side of 1852 has been checked and is empty. The rest has not.

documented