Circassian Names

Structure & order

Traditionally the socially-used name was patronymic + given name (in that order), plus nicknames; everyone in a clan also shared a common clan/lineage name (tlapq). Modern official forms diverge sharply by country of residence.

Schematic (homeland, modern Russian-administered form): `` [ClanSurname-ov/-ova] [GivenName] [Patronymic -ovich/-ovna] ` Schematic (traditional / diaspora oral usage): ` [ClanName(tlapq)] [Given] · [Patronymic] [Given] ``

See Name Ordering, Patronymics and Lineage.

Given names

Native Adyghe/Kabardian given names draw on Nart epic heroes, nature, and prized qualities (beauty, strength, horsemanship, nobility). Examples (romanized; native forms in Cyrillic where attested are not all confirmed in consulted sources: flag: thin):

• Sosriqwe: legendary Nart hero (m)
• Lhepsch: god/patron of blacksmiths (m)
• Shu "horseman"; Shuwey "knight / intrepid horseman"; Blaneshu "brave knight" (m)
• Seteney: "a beautiful flower of the drop-wort," central Nart matriarch (f)
• Zhan "princess / prince's unmarried daughter"; Zhanwes = zhan + wes "snow" (f)

A masculine ending -biy/-by (e.g. Nalbiy, Tolbiy) is reported as Turkic bey/bay "master, prince"; flag: contested etymology in the source itself. After Islamization, Arabic-origin names (Anwar "radiant," Murat "wish") and adoptions from neighbouring languages (Aslan < Turkish Arslan "lion"; Anzor < Georgian aznauri "free/noble") became common. Distinguishing genuinely native Adyghe names from these layers is a core difficulty.

Family names & patronymics

Clan/lineage names (tlapq). Descent is patrilineal; the tlapq ("blood frame"/clan) groups linear and collateral male relatives sharing one ancestor, and all members carry the clan name. Clan surnames are closely tied to tribal allegiance, e.g. Napso, Shoshha, Abrag. Napso is glossed as "whole-eyed" from Adyghe нэ (nă) "eye" + псэу (psăw) "alive/whole." Clans had associated emblems/tamgas.

Russian -ov/-ova overlay (homeland). Under Soviet civil registration it became obligatory to register surnames with Russian suffixes, -ov/-yev (men) and -ova/-yeva (women), with patronymics in -ovich/-ovna. Because most families lacked an official fixed surname, the father's name was often taken and suffixed. Many modern Kabardian/Adyghe surnames are thus Russified spellings of native clan names, e.g. Kushkhov ← Kabardian Qw'śẖä, Malbakhov ← Mälbaxwä, Akhokhov, Dzharimov. (Flag: individual native↔Russified mappings come from a single user-contributed source: treat exact spellings as indicative.) Post-Soviet revival movements have promoted reverting toward pre-Russification native forms.

Double surnames. A 2024 onomastics study (Ionov, Voprosy Onomastiki) finds double surnames arise differently by location: in the homeland from social events (family incidents, ransom from captors, adoption of a noble/wealthy family's name), whereas in Turkey they stem from state assimilation policy (see below).

Diaspora surname formation. - Turkey: the 1934 Surname Law (No. 2525) forced Turkish surnames; combined with bans on the Circassian language and renaming of villages, many families took Turkish names (e.g. one family → Gürsoy "strong lineage"). The native clan name often survives informally alongside the legal Turkish one. - Jordan / Syria: clan names like Napso, Shoshha, Abrag have often been preserved in an Arabic-naming environment, frequently functioning as the family name within Arabic given-name + surname conventions (see Arabic Names).

See Patronymics and Lineage, Russian Names.

How to address someone

Consulted sources gave no reliable detail on native Circassian honorifics or salutation formulas; flag: gap. In practice, address defaults to the surrounding state's conventions: Russian given-name + patronymic for respectful address in Russia (see Salutations and Address); Turkish Bey/Hanım in Turkey; Arabic honorifics in Jordan/Syria. The name-element -biy "master/prince" reflects a historic nobility register but is a name component, not a live salutation.

Pitfalls for software

• Three coexisting surname regimes. The same lineage may appear as a native clan name, a Russian -ov/-ova form, a Turkish surname, or an Arabic-context surname. Parsers must not treat these as different people/families.
• Russified gender suffixes (-ov vs -ova, -ovich vs -ovna) encode gender and must be handled like Russian Names, but the stem is a Caucasian clan name, not Slavic.
• Layered etymologies. Given names mix native Adyghe, Turkic, Georgian and Arabic origins; a Turkic/Arabic-looking given name does not imply non-Circassian identity.
• Order flips. Traditional patronymic-before-given order conflicts with Western/Russian given-before-surname order; the surface order alone is unreliable.
• Script switching. The same name appears in Cyrillic (RU), Latin (TR/IL), and Arabic (JO/SY); romanizations are inconsistent across communities.
• Sparse, single-source data. Circassian onomastics is thinly documented online; several name meanings and native↔Russified mappings here rest on one user-contributed or popular source and should be verified before high-stakes use.