Finding Someone You Served With Who Has a Very Common Name
You are not missing a name. You have the name, spelled the way he wrote it on a duty roster, and that is exactly the problem: several thousand living Americans have it too. Every guide written for this situation tells you to add a date of birth, an old address, a relative. You do not have any of those. What you have instead is a stretch of time in which the two of you stood in the same place under orders — and that turns out to be worth more, because the government that put you both there wrote it down, gave him a number no civilian database carries, and publishes a list of which parts of that file it will confirm about a living man to a person with no relationship to him at all.
The Short Version
A crowded name is a sorting problem, and for a veteran the sorting key already exists in writing. 5 U.S.C. § 552a(b) bars an agency from disclosing a record without the subject’s written consent unless one of twelve listed exceptions applies, the second of which is disclosure “required under section 552 of this title” — the Freedom of Information Act. Acting on that, the National Personnel Records Center publishes what it may release from a living veteran’s personnel file to a member of the general public: name, service number, dates of service, branch, final duty status, final rank, assignments and geographical locations, military education level, awards eligibility, a photograph, and place of entrance and separation. Read that list again as a veteran rather than as a researcher. Almost every entry on it is an episode — where a man stood and when — and an episode is the one thing you can test, because you were standing in it. Date of birth, the field every civilian guide puts first, is not on the list at all — not for a living veteran, and not for a deceased one, where the additions are place of birth, the date and geographical location of death, and place of burial. We work United States subjects who hold a real name as used in service; a first read typically comes back within 24 hours once the right man is identified, and we have done lawful public-records research since 2004.
Watch: Sorting Four Men Who Share One Name
The Tie-Breaker Was Issued to Him
The service faced this problem first, and solved it with a number.
Nobody who has been in a formation needs to be told that common names are common. The military knew it, and handled it the way it handles most things: administratively. Every service member is carried under a unique identifier distinct from his name, and it goes on the paperwork that follows him from induction to separation. Ask the archives for a file and you are asked for “the veteran’s complete name as used in service; service number; Social Security Number (if applicable); branch of service; dates of service; date and place of birth.” That parenthesis — if applicable — is doing real work: it marks the era boundary between men carried under a service number and men carried under a social security number, and which side of it your friend served on decides what identifier his file is filed under.
In the unit itself the same problem got a shorter fix. Where two men shared a surname, everyday practice was to hang the tail of the number on the name — the last four, on a laundry mark, a roster line, a range card, a sign-out board. You may have said those four digits out loud a hundred times without ever registering them as an identifier, because in that context they were just part of how the man was addressed. Nobody kept them. That is the central irony of this search: the discriminator existed, it was in daily use, and it is the one thing memory did not retain.
None of it reaches a consumer search tool. A people-search index is assembled from credit headers, marketing files, property and voter data. Service numbers are in none of those feeds. So a veteran typing a friend’s name into a free site is running a query against a system that has never held the field that would answer it, and the eight hundred results are not a failure of the site. If your subject is a civilian, stacking ordinary identifiers really is the method, and it is set out in breaking a tie on a common civilian name. This page is about the other case, where the identifiers you would stack were never yours to know.
Why "Get a Date of Birth" Is the Advice That Fails Here
Every general guide to a crowded name ranks date of birth first, and for a civilian subject that ranking is right. For this errand it is close to useless, and not because the field is hard to find. It is because the federal route open to you does not include it. Look at what the National Personnel Records Center publishes as releasable from a living veteran’s file and you will not find date of birth anywhere on it. Place of birth appears only in the short additional list that applies once the veteran has died. A living man’s birthday is the thing the release rule protects, and no amount of asking changes that.
So the advice has to be inverted for this reader. Stop trying to acquire the civilian discriminators you do not have. Work the ones the record will actually give up — and they are better than the ones you were reaching for, because you can check them against your own memory of a place and a year.
Four Men, One Name, One Afternoon
A worked illustration, not a real case – names and details invented to show how the released fields do the sorting.
| Candidate carrying the name | What the released fields showed | Verdict, and what settled it |
|---|---|---|
| Robert J., born about 1948, Ohio | No service record located under that name and spelling in the branch you named. | Out, provisionally. A nil result is not proof; a legal name change, a misspelling carried into the file, or the wrong branch would each produce it. Park him, do not delete him. |
| Robert J., born about 1950, Texas | Served, correct branch, but dates of service end two years before you arrived at the post. | Out, firmly. Dates of service are an episode, not an estimate. He cannot have been standing where you remember him standing. |
| Robert J., born about 1951, Georgia | Served, correct branch, overlapping dates, assignments and geographical locations include the installation you named. | Your man, pending confirmation. Two independent episodes agree. Confirm on a third before anyone is contacted. |
| Robert J., born about 1952, California | Served, correct branch, overlapping dates, assignments entirely on the other coast. | Out. This is the candidate a civilian filter keeps and a service record removes – right name, right era, right branch, wrong geography. |
| Robert J., deceased 2019 | Additional fields appear once a veteran has died: place of birth, date and geographical location of death, and place of burial. | Answered, and the errand changes. A burial place is a route to a widow or a child, and the letter you write is a different letter. |
What the illustration is really showing is that elimination here is cheap and confirmation is expensive. Three of the five went out on a single mismatched episode apiece, which took minutes. The one that survived is the one that needs work, because two agreeing fields is the point at which a searcher is most likely to stop early and be wrong. Notice also that the nil result at the top is the most dangerous row on the table: absence of a record feels like an answer and is not one.
What the Government Will Confirm About a Man Who Is Still Alive
A published list, and the two limits on it that matter most.
This is the part almost nobody outside the records world knows, and it is the reason this search is winnable. You do not need to be next of kin. You do not need his signature. You do not need to be related to him at all. In the archives’ own framing, you are “a member of the general public” if you are not the veteran and not his next of kin — and its guidance for requesters who are not the veteran or next of kin states plainly that without consent the centre “can only release limited information,” then publishes exactly what that limited information is.
The releasable set runs: name, service number, dates of service, branch of service, final duty status, final rank, assignments and geographical locations, source of commission, military education level, promotion sequence number, “awards and decorations (eligibility only, not actual medals),” a photograph, transcript of courts-martial trials, and place of entrance and separation. Where the veteran has died, three more appear: place of birth, date and geographical location of death, and place of burial.
Two limits, and they are not fine print. First, the archives mark salary, source of commission and promotion sequence number as “items rarely available in the records we maintain,” so build nothing on those three. Second — and this catches people every time — an address is not on the list, and never will be. The government will tell you which man of that name served where and when. It will not tell you where he lives now, and it does not have a mechanism to pass a letter along for you. Confirming identity and locating a person are two different jobs, and the second one is not a federal service.
The scope of the rule matters too. This release framework applies to files that are still in federal custody rather than to the older ones that have passed into the archives’ own hands, where a different and much more open regime takes over. Which side of that line your friend’s file sits on, what it costs to ask, and what happens when the file itself no longer exists are a whole subject on their own, worked through in requesting a service file from the National Archives.
Where a Crowded Service Name Beats a Searcher
Four failures that look like a dead end and are not.
Two of them were in your company
A shared unit is not a unique key. Where a surname doubled up, the unit disambiguated with the tail of the number and you were never told what it was. If the released assignments match for two candidates, go to rank progression and education level – those diverge even when the postings do not.
Junior and senior, same everything
A father and son carrying one name, one branch and one home of record is the hardest version of this and it is not rare. Dates of service separate them cleanly; ages and addresses do not, and a consumer index will have merged them long ago.
You are searching a branch he left
Inter-service transfers, reserve components and a National Guard period all put a man’s record somewhere other than where you would look. The branch you served alongside him in is not always the branch that holds his separation.
You aged him from your own memory
Everyone in a photograph looks nineteen. Filtering candidates on a guessed birth year quietly discards the right man, and because you never see what the filter removed, the search feels thorough right up until it fails.
An Attribute Says Who He Is. An Episode Says Where He Stood.
This is the axis a fellow soldier can test and a database cannot.
Consumer people-search is built on attributes — durable properties that cling to a person: an age, an address, a relative, a phone number. Attributes are what a marketing file can carry, and they are also what every same-name stranger has a version of, which is why adding one narrows a pool only a little unless it is very precise.
A personnel file is built on episodes instead. Dates of service is an episode. Assignments and geographical locations is a list of episodes. Place of entrance and separation is the first and last of them. An episode is not a property of the man; it is a claim about a specific place at a specific time, and it is either true of him or it is not, with no partial credit and no near-misses.
That distinction is why a buddy is a better searcher than a professional working from a file. You do not have to guess whether an assignment is plausible. You were there. If four men in the country carry the name and the released dates of service show one of them at a post you can name in a year you can name, the other three are gone — not down-ranked, gone. No civilian discriminator does that, because no civilian discriminator is a fact you personally witnessed.
Test the episode against paper rather than memory wherever you can, because memory compresses. Your own separation document carries your dates, your unit and your station; old orders name a reporting date and a duty location; the citation on an award names an action and a period. Those were issued to you, they describe the same weeks you shared, and no rule restricts your access to your own file. Where the person you want is one name on a list of ninety rather than a single friend, the work is organised completely differently and the unit’s own paperwork becomes the spine of it — that job is laid out in finding a whole unit’s veterans for a reunion.
From a Confirmed Identity to a Living Person
What we do after the name resolves, and the two things we will not do.
Once the right man is identified rather than guessed, the remainder is ordinary public-records work and it is no longer a military problem: address history, property and court indexes, relative associations, the paper an adult life leaves behind, until one living person is verified rather than assumed. That last stretch is what our skip tracing work covers. We work subjects inside the United States, and we need a real starting identifier — the name as it was used in service, the branch, and a window of years. A nickname on its own, or a man who separated and settled abroad, is not something we can run, and we would rather say so now than take the case and hand it back.
There is a boundary here that matters more in this errand than most people expect, and it is not a disclaimer. A service connection is exactly the story a person uses to justify a search that should not happen. We decline any request where the apparent purpose is locating someone protected by an order of protection, or someone who relocated because of domestic violence or stalking. No shared deployment makes that acceptable. If you are the person being looked for: most states run an address confidentiality program that substitutes a designated address on public filings, and the court that issued your order can reach records and impose consequences no private party can. Those are the right routes and they work.
The quieter boundary is about the man himself. Some veterans put the service down deliberately and did not tell anyone where they went. A confirmed identity is not a claim on him. We locate; we do not knock on doors, we do not make contact on your behalf, and we do not pass your details to anyone. Write a short letter, say who you are and which unit and which year, and make it easy for him not to reply. If the answer is silence, that is an answer. And if what you actually need is the wider map of where veterans surface — associations, reunion networks, the routes that do not start from a record — that is the wider guide to tracing a long-lost service friend.
How the Search Runs
From a shared name to one verified living person.
Send the Name and the Overlap
The name as he used it in service, the branch, and the window you were together – a post or a ship, and the years. If you still hold your own separation document or orders from that period, the dates on them are better than your recollection of them.
We Build the Candidate Pool
Every living person in the United States carrying that name in the plausible age band, assembled before any of them is favoured, so that elimination is provable rather than a story about the first one we liked.
We Test Each One Against the Episodes
Service-record fields and public records are worked against the place-and-time claims you supplied. A candidate is removed on a mismatched episode, and the reason is recorded rather than discarded.
You Get One Person and the Reasons
A verified current name and location for a living veteran, the evidence the identification rests on, and a plain account of which near-matches were ruled out and why. What you do next is yours, and what he does next is his.
Who Runs This Search
Four people who arrive at the same crowded name from different directions.
Veterans Reconnecting
You have carried the name for thirty years and every search returns a wall of strangers. You are the one person who can confirm an assignment, which is why this is winnable.
Families of the Late
A widow or a son working from a photograph and a story, trying to reach the men who were there. Different standing, same sorting problem.
Unit Historians
A name in a citation or a caption that resolves to a dozen people. One confirmed identity is worth more to a history than ten plausible ones.
Estates and Benefit Filers
Where a shared name has to be resolved to satisfy someone else – an administrator, a claims examiner, a records office – a documented elimination matters as much as the answer.
Our Commitment
We identify which person carrying that name is the veteran you served with, and we say how we know. Where the record cannot reach him, we say that instead. We have done lawful public-records research under a permissible purpose since 2004, for United States subjects, and a first read typically comes back within 24 hours once the right man is identified. We never make contact on your behalf, we never conduct surveillance, and we decline any search whose purpose looks like locating someone who left for their own safety.
Frequently Asked Questions
His name is shared by thousands. What can I get about a living veteran without his permission?
More than most people expect, and it is published rather than discretionary. Under 5 U.S.C. § 552a(b) an agency may not disclose a record without the subject’s written consent unless one of twelve listed exceptions applies; the second is disclosure “required under section 552 of this title,” which is the Freedom of Information Act. Acting on that, the National Personnel Records Center lists what it may release from a living veteran’s personnel file to any member of the public: name, service number, dates of service, branch, final duty status, final rank, assignments and geographical locations, source of commission, military education level, promotion sequence number, awards and decorations “eligibility only, not actual medals,” a photograph, transcript of courts-martial trials, and place of entrance and separation. You need no relationship to him for any of it.
Is there any way to get more than the limited list?
Two ways, and neither is a loophole. The veteran can authorise it himself: a signed statement specifying what may be released to you, which is not much use before you have found him but is very useful afterwards if you need something for a history or a claim. Or, where the veteran has died, his next of kin can request the full file — and the archives define next of kin narrowly, as “the un-remarried widow or widower, son, daughter, father, mother, brother or sister,” with proof of death required. A friend, however close, is not on that list, and no one here will sign a form claiming to be. Everything this page describes is done as an ordinary member of the public.
How do I actually send the request as someone with no relationship to him?
You send it in your own name and say what you are: not the veteran, not next of kin. There is no special standing to establish and nothing to swear. The archives note that the Standard Form 180 is “not mandatory” but is the recommended route because the form “captures all the necessary information to locate a record” — which is the real difficulty, since a record is retrieved on identifiers rather than found by browsing. Give the name as used in service, the branch, and the tightest window of dates you can defend, and put your own separation document dates in the letter if they bracket his service. A request that cannot be matched to a file comes back empty and tells you nothing about the man.
Two candidates both served in the right branch at the right time. How do I break that?
Go to the fields that vary between individuals rather than between cohorts. Assignments and geographical locations is the strongest, because two men in the same branch and era usually diverge somewhere in their posting history even if they overlapped once. Final rank and military education level are next, since promotion timing and course attendance are individual. Place of entrance and separation often splits them outright. If two candidates still agree on everything you can obtain, stop and treat both as unconfirmed rather than picking the more plausible one.
I remember his nickname and his last name. Is that enough to start?
Not on its own, and it is fairer to say so than to take it. The archives ask for the name “as used in service,” and a nickname is precisely what a file does not carry. What can rescue it is the paperwork on your side rather than his: your own separation document names your unit and station, and a unit at a given date is a bounded group of people rather than an open field, so a surname inside it is a far smaller problem than a surname in the country. Bring the surname plus the branch and the window and there is something to work with.
Nothing comes back under his name at all. Does that mean he never served?
No, and treating a nil result as an answer is the commonest way this search goes wrong. A file is retrieved on the name as used in service, so a later legal name change hides it. A misspelling entered at induction follows the man for his whole career. A component or branch you did not expect puts the record somewhere else. And separately from all of that, some older files no longer exist to be found. Absence of a record is a reason to widen the spelling and the branch, not a reason to conclude anything about the man.
What if he has died, or does not want to hear from me?
Both happen, and they need different things from you. If he has died, the errand quietly becomes a different one: the people to write to are a widow, a son or a daughter, and what they usually want from you is not condolence but the thing only you have — a few paragraphs about who he was at twenty, which no record anywhere holds. Say that first, and ask for nothing. If he is alive and does not answer, assume he read it and chose not to reply, and do not send a second one through a relative or an employer — that is the point at which a reunion attempt starts to feel like pressure to the person receiving it. Give him a way to reach you and no way to be reached again.
What do you need from me, and how long does it take?
The name as he used it in service, the branch, and the window you overlapped — a post, a ship or an installation, plus the years. Anything you still hold from that period is worth more than your memory of it: your own separation document, orders naming a reporting date, an award citation naming a period. Tell us the approximate age band and any state you associate with him. We work United States subjects only. Once the right man is identified, a first read typically comes back within 24 hours.
One Name, Too Many Men Carrying It?
Send the name as he used it in service, the branch, and where and when you served together. We build the pool, test each candidate against the record, and come back with one person and the reasons. Contact us to get started.
Start Your Request →
