A collision built from two different kinds of common
"John Kim" is not common the way "Michael Johnson" is common, by the ordinary math of two frequent names meeting at random. It is common because each half of the name is common for a distinct historical reason, and those two reasons happened to reinforce each other inside one specific population: Korean immigrants to the United States and their US-born children.
Kim is common because Korean surnames are extraordinarily concentrated compared with surnames in most of the world. A small number of family names cover a very large share of the population, and Kim is the largest of them by a wide margin. John is common because, for most of the last thousand years of Christian Europe and its diaspora, John was close to the default name given to a baptized boy — and it remains, to this day, the standard English rendering of a name that appears directly in Christian scripture. Neither fact has anything to do with the other. Korea's surname history runs through medieval clan registries and a nineteenth-century collapse of a hereditary class system. The popularity of "John" runs through the Gospels, the Crusades, and a thousand years of European baptismal naming. They meet only because of a third historical fact: Korea, unusually among East Asian nations, became a heavily Christian country, and its immigrants to English-speaking countries adopted English given names at scale — disproportionately biblical ones.
This page is the frame for that whole story. The four guides beneath it each take one piece of it seriously enough to explain the mechanism, not just state the fact: why Korean surnames concentrated the way they did, why the same Korean name ends up spelled several different ways in the Latin alphabet, why John specifically (and not some other name) became the default English choice, and what a careful, honest estimate of "how many John Kims" actually looks like once the math is done properly.
Kim: concentrated by history, not by chance
In most of the English-speaking world, surnames are relatively distributed. The most common American surname, Smith, accounts for well under 1% of the US population. Korean surnames do not work that way. Government census figures from Statistics Korea put Kim at roughly 21.5% of the national population on its own — meaning something close to one in five people in South Korea shares that single surname. Add the next two most common surnames, Lee and Park, and the top three alone account for close to 45% of the country.
That concentration is not a linguistic accident. It traces to a specific historical process: for most of Korea's premodern history, surnames were a privilege largely restricted to the aristocratic yangban class, and the majority of the population — commoners, and especially the lowest social classes — had no registered surname at all. When Korea's hereditary class system was formally dissolved in the late nineteenth century and everyone was required to register a family name, large numbers of newly surnamed people took names already associated with the aristocracy, Kim chief among them. A separate guide on this hub, on why Kim is the most common Korean surname, works through that history in detail, along with the bon-gwan (clan-seat) system that Korean families still use today to distinguish one Kim lineage from another when the surname alone cannot.
One Korean name, several English spellings
Even after a Korean family is uniquely identified by surname and clan, a second layer of collision gets added the moment that name is written in the Latin alphabet. South Korea's official transliteration standard, Revised Romanization of Korean, would technically render 김 as "Gim." Almost nobody does. The overwhelming majority of people with this surname write it "Kim" — an older, non-standard spelling so deeply entrenched in passports, English-language documents, and personal habit that the government standard has never displaced it in practice.
That is not a quirk unique to this one surname. Korean has changed its official romanization system more than once in the last century, earlier conventions remain in wide informal use alongside the current one, and Korean passport regulation itself does not force a single "correct" spelling — it permits a defined set of alternatives and, as recent Korean court rulings have confirmed, treats established personal usage as a legitimate basis for keeping a non-standard spelling. The practical result is that one Korean name can map to more than one Latin spelling, and — just as important for a disambiguation problem — spellings that look identical in English can sometimes trace back to different underlying Korean names. A dedicated guide on this hub, on Kim, Gim, and Korean romanization, explains the two competing romanization systems, why "Kim" persists despite the official rule, and how the identical problem shows up in given names.
Why John, specifically
The given-name half of the collision needs its own explanation, because "John" was not an arbitrary pick from a large menu of English names. Two separate facts push toward it. First, John has an unusually strong claim on being the default Christian baptismal name in the first place — it is the English form of a Hebrew name that appears directly in the New Testament, carried by two of Christianity's most venerated figures, John the Baptist and the Apostle John, and it was, for centuries, the single most common male given name across Christian Europe. Second, Korea itself became — unlike most of the rest of East Asia — a substantially Christian country, particularly among Protestant and Catholic congregations that trace back to nineteenth-century missionary activity, and the practice of Korean immigrants and Korean-Americans adopting an English given name in addition to (or instead of) a Korean one is well documented, common, and disproportionately drawn from biblical names.
Put those together and the mechanism is straightforward, even if no single part of it was inevitable: a Christian-heavy immigrant population, choosing English names from a pool weighted toward scripture, converging on one of history's most heavily used Christian names, layered on top of a surname that a fifth of an entire country already shares. A guide on this hub, on why John is common among Korean-Americans, lays out the history of Christianity in Korea, the English-name-adoption practice itself, and how it varies by generation.
Doing the collision math without cheating
It is tempting, once both halves of the pattern are visible, to multiply a surname frequency by a given-name frequency and produce a tidy number of "how many John Kims there are." That shortcut is wrong, and it is wrong in an instructive way. Given-name frequency in the general US population is not evenly distributed across every surname group; it varies enormously by the ethnic, generational, and religious makeup of the people who share a surname. "John" is not randomly distributed among people named Kim the way it might be among a random sample of the whole country — it is concentrated there for the specific historical reasons described above, which is exactly what naive multiplication ignores. A separate guide, on how many people are named John Kim, walks through US Census Bureau surname-frequency data and Social Security Administration given-name data side by side, explains precisely why the naive multiplication fails, and states plainly what can and cannot be known with the public data that actually exists.
What the name explains, and what it does not
None of this history explains who any particular John Kim is. It explains why the question "which John Kim?" is a real, structural problem rather than a strange coincidence — why a search engine, a hospital directory, or a professional network cannot resolve the name to one person the way it usually can with a rarer name. The other three silos on this site document real, individually verified people who happen to share this name, organized by the field they work in. This one is different by design: it contains no individual records, no biographies, and no names beyond "John Kim" itself. Its job is to make the collision legible — to show, with sourced history and government data rather than guesswork, exactly why this particular combination of a surname and a given name turned out to be shared by so many unrelated people at once.