Note Wisdom
This note explains why hams use "73" as a sign-off, tracing it to the Phillips Code of the telegraph era, where it meant "best regards." It covers the related code 88, the debate over "73s" versus "73," the musicality of Morse rhythm, and the unresolved questions about the word "ham" and regional variations.
If you spend any time around amateur radio, you will notice something odd. Emails end with "73." Forum posts sign off with "73." Even casual messages between operators sometimes close with that number instead of "Best" or "Regards." To an outsider, it looks like a code. It is. The number 73 carries a specific meaning that stretches back to the age of telegraphy, and the story of how it became a standard sign-off in ham radio is more interesting than you might expect. It involves a forgotten shorthand system, a debate about grammar, a bit of musicality, and a few side notes that range from the affectionate to the unfortunate. What follows is a reader's guide to what the material actually says about 73, where the explanation is clear, where it gets messy, and what a newcomer should take away.
The central explanation is straightforward. The use of 73 as a sign-off comes from something called the Phillips Code. This was a system devised in the telegraph era to speed up the transmission of common messages by mapping them to numbers. Instead of spelling out a phrase letter by letter, an operator could send a short number and the receiving operator would know what it meant. It was a form of shorthand for the wire.
In that code, 73 mapped to "best regards" or "my compliments." It was intended as a general valediction, a way to close a transmitted message politely and efficiently. That is the core of the answer. The number was not arbitrary. It was part of a larger system designed to save time and reduce errors on busy telegraph lines.
When amateur radio emerged, it inherited much of the operating culture of commercial and military telegraphy. Morse code was already the foundation of radio communication, and the conventions that went with it came along for the ride. Operators who had learned their craft in the service or in commercial stations brought the Phillips Code with them. Over time, the code faded from commercial use, but a few of its numbers stuck. 73 was one of them. It survived because it was useful, because it was short, and because it became a habit. Today it is used not just in Morse code but in voice contacts, emails, forum posts, and casual conversation among hams. It is jargon, but it is jargon with a pedigree.
One detail worth noting: the material mentions that 73 was a general valediction, not a romantic one. That distinction matters because there is a related code, 88, which maps to "love and kisses." The material explains that 88 sometimes takes the place of 73 for communications between affectionate parties. That is a useful clarification for anyone who has seen 88 and wondered what it meant. It is not a variation on 73; it is a separate sign-off with a different emotional register. The source treats this briefly, almost as an aside, but it is a helpful piece of context. If 73 is a handshake, 88 is a hug.
The material also mentions a less-used code, 99, which one note describes as possibly unofficial and meaning something along the lines of "go for a hike someplace warm." That is a humorous interpretation, and the source does not present it as a standard. It is more of a curiosity, a reminder that the Phillips Code had many entries and that not all of them survived into modern use. The fact that 73 and 88 are the ones that stuck tells you something about what operators valued: a polite closing and, occasionally, a warm one.
Once you understand that 73 already means "best regards," a grammatical problem appears. If you write "73s," you are effectively saying "best regardses." That is the point one part of the material makes, and it does so with a sense of humor. The comparison to Gollum from The Lord of the Rings—talking about "Hobbitses"—is memorable, even if it is a bit silly. The underlying argument is serious, though. 73 is already a complete phrase. Adding an "s" to pluralize it does not make it more correct. It makes it redundant.
But the material does not stop there. Another perspective argues that "73s" can make sense in certain contexts. If you are addressing a group or a net with multiple people, saying "73s" could be a way of extending best regards to everyone listening. It is not grammatically pure, but it is communicatively clear. That is the tension. One view treats 73 as a fixed unit that should not be altered. Another view treats it as a word that can be pluralized when the situation calls for it.
The source notes something interesting about how this plays out in practice. On CW, operators rarely send "73s." The plural form is more common on SSB or in written messages. On CW, it is not unusual to hear "73" repeated—"73 73"—even when signal conditions do not require repetition. That repetition is not about grammar. It is about rhythm, emphasis, and the musicality of the code. Sending 73 twice has a different feel than sending it once. It is a way of signing off with a little extra warmth or finality. The material does not say this explicitly, but it is implied by the contrast between "73s" on voice and "73 73" on CW.
I found this part of the source a bit hard to follow at first. The debate about "73s" versus "73" is not resolved. The material presents both sides without declaring a winner. One note says that "73s" may be redundant but is certainly not transmitted with malicious intent, and that the writer lets it go. That is probably the most practical position. Language changes. Conventions drift. If someone writes "73s," you know what they mean.
Article + Bundle Download
Full 6-lecture collection
All contents below are exclusive to the paid Word file, NOT available on this web page
This isn’t one long read. It’s a modular study kit about why hams say “73,” where it comes from, and how sign-off culture works. Use this guide to see what’s available, then jump to the part you need.
For when you have five minutes — or just want the bottom line on 73.
For when you want to understand the history and test your own judgment about sign-off conventions.
For when you want to know what the community debates, what beginners get wrong, and how 73 plays out in real stations.
For when you need to practice, build club resources, or write something.
For when you want a structured path and reliable tools to learn more about ham jargon and culture.
For when you want to build a habit of reflection and go deeper on your own.
The premium document contains conclusions, questions, concepts, a glossary, debates, misconceptions, case studies, an action checklist, essay templates, research topics, citation formats, study FAQs, a toolkit list, a 7-day plan, note-taking space, and a verified reading list.
Start with Category 1 to orient yourself. Use Categories 2–5 to go deep. Finish with Category 6 to reflect and extend.
There is also a more serious note buried in the discussion. One contributor points out that 88, the code for "love and kisses," has been adopted as a symbol by neo-Nazis because the letter H is the eighth letter of the alphabet, and "HH" stands for a hateful phrase. That is a real-world complication that the original telegraph operators could never have anticipated. The material does not dwell on it, but it is a reminder that symbols can be appropriated and their meanings can shift. For most hams, 88 still means "love and kisses." But the note is there, and it is worth being aware of.
One of the more interesting parts of the material is the discussion of rhythm. A contributor notes that codes like 73 were used not just because they were short but because they had a distinctive and musical signature. In Morse, every character has a rhythm. A good operator does not just send dots and dashes; they send them with a certain flow, a certain cadence. The number 73 has a rhythm that is pleasant to hear and easy to recognize. That rhythm is part of why it stuck.
The material includes a personal anecdote about learning rhythm from a navy father. The exercise is described as "best bent wire / g," which is apparently a phrase used to practice the feel of Morse. The contributor says that trying it on a Morse key improves musicality. I cannot verify the exercise myself, and the source does not explain it in detail, but the broader point is clear: Morse is not just a technical skill. It is a performance. The best operators make it sound good.
This connects to the origin of the word "ham." The material notes that some early non-military operators were not skilled at sending, and their poor fist—their clumsy keying—made them sound "ham-fisted." That is where the term "ham" supposedly comes from. I have seen other explanations for the word, and the source does not present this as definitive. But it fits the theme. In the early days of radio, operating skill mattered. A good operator could be recognized by their rhythm. A bad one could be recognized by their lack of it. Codes like 73 were part of that culture of skilled, musical communication.
The material does not spend a lot of time on this. It is a side note, a bit of color. But it explains something about why 73 feels the way it does. It is not just a word. It is a pattern. When you hear it on CW, you recognize it instantly, the way you recognize a familiar voice. That familiarity is part of its value. It signals the end of a contact in a way that is both efficient and pleasant.
The material leaves a few things unresolved. The biggest is the "73s" question. Is it wrong? Is it acceptable in group settings? The source does not give a final answer. It presents the redundancy argument and the plural-for-a-group argument and lets the reader decide. I suspect that most operators do not care much either way. The ones who do care tend to feel strongly, but they are a minority. For a beginner, the safest approach is probably to use "73" on CW and "73" or "73s" on voice or in writing, depending on the context. Nobody is likely to complain.
Another open question is the origin of the word "ham." The material offers one explanation—ham-fisted operators—but does not cite a source or acknowledge other theories. I have read elsewhere that the word might come from the initials of an early station, or from a derogatory term used by professional operators for amateurs. The source does not engage with those alternatives. It presents the ham-fisted story as if it were settled. That is a weakness. A more careful treatment would note that the etymology is disputed.
The material is also thin on the transition from telegraphy to amateur radio. It says that 73 survived because operators brought it with them, but it does not explain how or when that happened. Was it immediate? Did it spread through military service? Did it come through commercial stations? Those details are missing. The reader is left to infer that the culture simply carried over. That is probably true in broad strokes, but a little more specificity would help.
One more thing that the material does not address: how 73 is used outside the United States. The Phillips Code was an American invention, and the source treats 73 as a universal ham convention. But are there regional variations? Do operators in other countries use different codes or different sign-offs? The material does not say. Given that amateur radio is a global hobby, that seems like a gap worth filling. It may be that 73 is truly universal, but the source does not confirm it.
None of these gaps are fatal. The core explanation—73 comes from the Phillips Code, where it meant "best regards"—is solid and well-supported. The surrounding details are interesting, even if some of them are speculative. For a reader who just wants to know why hams say 73, the material answers the question clearly. For a reader who wants a deeper history, there is more work to do.
What I take away from all this is that 73 is more than a habit. It is a fragment of history that survived because it was useful and because it felt right. It is short, clear, and musical. It carries a meaning that everyone in the hobby recognizes. It has a grammar debate attached to it, a bit of cultural color, and a few unresolved questions. That is a lot for a two-digit number. But that is what happens when a convention lasts long enough. It accumulates meaning. It becomes part of the identity of the people who use it. And it becomes something that outsiders notice and wonder about. 73 is not just a sign-off. It is a small piece of the culture of amateur radio, and it is worth understanding.
Skip hours of watching lectures. Get organized notes, exam prep materials and problem solutions all in one Word file.
Click to see everything included
All contents below are exclusive to the paid Word file, NOT available on this web page
This isn’t one long read. It’s a modular study kit about why hams say “73,” where it comes from, and how sign-off culture works. Use this guide to see what’s available, then jump to the part you need.
For when you have five minutes — or just want the bottom line on 73.
For when you want to understand the history and test your own judgment about sign-off conventions.
For when you want to know what the community debates, what beginners get wrong, and how 73 plays out in real stations.
For when you need to practice, build club resources, or write something.
For when you want a structured path and reliable tools to learn more about ham jargon and culture.
For when you want to build a habit of reflection and go deeper on your own.
The premium document contains conclusions, questions, concepts, a glossary, debates, misconceptions, case studies, an action checklist, essay templates, research topics, citation formats, study FAQs, a toolkit list, a 7-day plan, note-taking space, and a verified reading list.
Start with Category 1 to orient yourself. Use Categories 2–5 to go deep. Finish with Category 6 to reflect and extend.
Article + Bundle Download

