DnD party names (or group names): what one 200-name batch actually gives you
A party name is usually a surname, a trade, or a deed. The generator on this site only makes person names, so the useful question is what a real batch of them hands over: how many surnames arrive with more than one bearer, how often a five-person party ends up sharing one, and which surname is safe to put on the banner. Below is the count from 10,000 generated names, not a list of suggestions.
Sample and method, before any conclusion.
50 batches of 200 names — 10,000 names in total. Seed 20261021, gender Neutral, the five styles (gritty, noble, archaic, wild, grim) cycled in order, five cultures per batch rotated so all 36 appear across the run, and one batch tracker per batch, so the inside-a-batch caps are computed for n = 200, the largest single pull on the site. The batch loop rejects duplicate names and repeats the same lead-syllable check the tool uses.
Surname = the second word of a generated name. Solo surname = one that appears once inside its batch. Shared surname = the same surname on two members of one party. Party draws: 2,000 parties per batch at each size, so 100,000 per size, from a seeded stream, which is why the rates below repeat exactly when you rerun the script. Everything here is counted from that run; nothing is estimated.
The answer, before the tables
- One family, one company, one house: take a surname that already has two or three bearers in your batch and put it on the banner. An average batch gives 16 of its 200 names a surname that someone else in the same batch also carries, so a candidate usually exists.
- A mixed crew: take five solo surnames, one per member. The average batch holds 184 surnames that appear exactly once, and one batch in the run held 200.
- Do not build the name out of a given name. 10,000 names produced 9,759 distinct given names, so a given name points at one person. Name the party after a surname, a place or a deed, and let the given names belong to the members.
What the 10,000 names show
1. The full names do not repeat, but the surnames do. Filling 50 batches of 200 took 10,000 draws and rejected 0 duplicates: 10,000 names, 10,000 distinct. Those 10,000 names carry 1,183 distinct surnames — 192.1 per batch — so 16 of the 200 names in an average batch share a surname with at least one other name. The novelty is in the given name. The house name is the part that repeats, and that is exactly the part a party is usually named after.
2. A five-person party drawn blind shares a surname 16 times in 20,000 — 0.08%. At four members it is 5 in 20,000 (0.025%), at six 10 in 20,000 (0.05%), though at this sample size the gap between four and six is noise. A shared given name at five members happens once in 20,000. So when two members of a party read like siblings, the surname did it, and the odds of that are low enough that a party picked at random is fine — but high enough that a party picked by eye from the top of a list is worth checking.
3. Surnames travel between batches; full names do not. Of the 1,183 surnames in the run, 1,177 turned up in more than one of the 50 batches, and Stonefist appeared in 29 of them. Of the 10,000 full names, none repeated, even across batches. A banner built on a surname stays consistent with the villages and NPCs you generate next week; a banner built on a full name is a one-off that will not match anything.
The numbers
| Party size | Parties drawn | Shared surname | Share |
|---|---|---|---|
| 4 | 100,000 | 1,661 | 1.66% |
| 5 | 20,000 | 16 | 0.08% |
| 6 | 100,000 | 3,972 | 3.97% |
Same draws, shared given name: 1 of 20,000 at four members, 1 at five, 1 at six.
| Surname | Bearers | Share | Batches |
|---|---|---|---|
| Grovekeeper | 23 | 0.23% | 13 |
| Skywing | 23 | 0.23% | 16 |
| Wildbound | 23 | 0.23% | 14 |
| Wildrevel | 23 | 0.23% | 14 |
| Grimfist | 22 | 0.22% | 14 |
| Oakmantle | 22 | 0.22% | 13 |
| Willowbound | 22 | 0.22% | 16 |
| Ironfist | 21 | 0.21% | 14 |
| Oakkeeper | 21 | 0.21% | 15 |
| Rootleaper | 21 | 0.21% | 14 |
| Rootshade | 21 | 0.21% | 13 |
| Stonefist | 21 | 0.21% | 17 |
| Vinemantle | 21 | 0.21% | 13 |
| Wildmantle | 21 | 0.21% | 13 |
No surname carried more than four names inside one batch — the batch cap — and none reached it in this run; the busiest was three.
| Cultures in the batch | Distinct surnames | Names sharing one |
|---|---|---|
| Human, High Elf, Wood Elf, Drow, Half-Elf | 140 | 102 |
| Hill Dwarf, Mountain Dwarf, Duergar, Lightfoot Halfling, Stout Halfling | 116 | 151 |
| Forest Gnome, Rock Gnome, Half-Orc, Orc, Dragonborn | 147 | 106 |
| Kobold, Tiefling, Aasimar, Fire Genasi, Water Genasi | 170 | 58 |
Same 200 slots, same caps, different cultures: the dwarf-and-halfling batch packed 200 names into 116 surnames, while the genasi-and-tiefling batch spread over 170. If a batch feels like one village, that is the culture mix rather than the count — draw fewer dwarf and halfling cultures when you want a party that does not read as one clan.
Surnames from this run, used as party names
A house or a family. Pick the surname with the most bearers in your own batch and put it in front of the word House. In this run Grovekeeper carried 23 bearers across 13 batches, so House Grovekeeper describes an organisation the rest of the campaign can meet: Wobanath Grovekeeper, Hasonamil Grovekeeper and Thanir Grovekeeper are already members of it. The generator supplies the surname; the word in front of it is yours.
A company or a crew. Same surname, a trade word after it — Stonefist Company, Grovekeeper Company, Ironfist Company. This is also how a guild name works: a guild is a house with more members, and the collision numbers above do not change because you added a trade. Thogramund Ironfist, Mukhonar Ironfist and Krethumikh Ironfist came out of one batch and read as a company rather than three strangers.
A party that is not a family. Take five solo surnames from one batch and let the banner come from something the party did or somewhere it has been. One batch in this run gave a clean five with no surname shared twice: Murard Marrowmoor, Ragedor Silverbough, Fasimeth Galewind, Nosyn Ashveil, Lacenan Nighthollow. The same pull also shows the failure case — Lifawyn Nighthollow and Fadhelath Nighthollow arrived alongside Lacenan, three bearers of one surname in one batch. That is a company, not a party; if you wanted a mixed crew, reroll instead of writing around it.
Questions this page answers
Will two players in one batch get the same name?
No. Fifty batches of 200 took 10,000 draws and rejected every duplicate: 10,000 names, 10,000 distinct.
Will they share a surname?
Often. The 10,000 names carry 1,183 distinct surnames, about 192.1 per batch, so 16 of the 200 names in an average batch share a surname with someone else in the same batch.
How likely is a five-person party to share a surname?
0.08% over 20,000 parties. Sharing a given name is far rarer: 1 in 20,000.
What should I name the party itself?
A surname that already has two or three bearers in the batch, or a place or deed. Given names are close to unique here (9,759 distinct in 10,000), so a given name points at one person, not a group.
Reproduce it
The script behind these tables is on this site at /assets/party-stats-v2.js. Open any page here, open the browser console, and paste one line:
var s=document.createElement('script'); s.src='/assets/party-stats-v2.js'; document.body.appendChild(s);It reruns the 50 batches at seed 20261021 with the same culture rotation and prints three tables: party-size clashes, the surname table above, and the per-batch spread. The party draws use their own seeded stream, so the clash rates come back identical instead of drifting a hundredth of a percent. Change SEED, BATCHES, PER_BATCH, SIZES or PARTIES at the top of the file for a different sample of the same generator.
Related: sixty cool D&D names sorted by register, 30,000 names measured for openings, closings and clans, and the guide index. Back to the generator.