KN is a super practical Morse procedural signal because it controls the flow. It’s basically “your turn — and I mean YOU specifically.” If you’re practicing real CW-style exchanges (or just want your transmissions to sound clean), KN is how you hand over the conversation in a disciplined way.
People often search for things like:
What does KN mean in Morse code?
What is KN in Morse code?
How do you tell one specific station to respond in Morse code?
What does -.–. mean in Morse code?
How do you invite a reply in CW?
This page gives you the exact KN pattern, what it means, how timing works, and how to practice it so you use it correctly.
KN in Morse code: the exact pattern
KN = -.–.
That’s:
dash, dot, dash, dash, dot
Written clearly:
-.–.
What KN means (in plain English)
KN means:
Go ahead / transmit — but only the station I’m calling.
Think of it as:
“My message is done, and I’m handing the mic to one specific station.”
You’ll see it in directed contacts, nets, and any structured back-and-forth where you don’t want random stations jumping in.
KN vs other “flow” signals (don’t mix these)
KN is not “end of message.”
AR = end of message block (clean break)
SK = end of contact (final sign-off)
K = invitation for any station to reply (“over”)
KN = invitation for the specific called station to reply (directed “over”)
If you want anyone to answer, use K.
If you want ONLY the station you called to answer, use KN.
Timing rules for KN (this is the whole game)
Morse timing uses units:
Dot = 1 unit
Dash = 3 units
Gap between elements inside one character = 1 unit
Gap between characters = 3 units
Gap between words = 7 units
KN is sent as a single procedural signal, meaning you send -.–. with normal inside-character spacing (1 unit between each element), then you separate it from surrounding text with the standard character gap.
So KN should feel “tight” inside:
-.–.
Then a clear pause after it (3 units) before the other station replies.
Common KN mistakes (avoid these)
Sending it like two letters (K + N)
K = -.-
N = -.
That is NOT KN.
KN is the procedural signal -.–. sent as one pattern.
Using K when you really mean KN
If you’re in a directed exchange and you send K, you’re basically opening the door for anyone to respond. In nets or busy frequencies, that can get messy fast.
Bad spacing inside the signal
If you insert character gaps inside KN, it stops sounding like a single signal and becomes confusing. Keep inside gaps 1 unit.
Using KN without clearly calling a station first
KN assumes you have a specific station in mind. Usually you call their callsign (or identifier), then end with KN to give them the floor.
How to use KN (simple examples)
Example 1: Directing a reply to one station
CALLSIGN MESSAGE KN
Meaning:
“I’m done, and ONLY you respond now.”
Example 2: A structured exchange
CALLSIGN PART ONE AR
CALLSIGN PART TWO KN
Meaning:
Message block ended cleanly, then you explicitly hand over to that station.
Example 3: Net-style directed traffic
STATION1 DE STATION2 INFO KN
Meaning:
“This is for you, reply when ready.”
Practice drills (fast and effective)
Drill 1: Rhythm lock
Send KN ten times:
-.–.
Focus on:
dash strong, dots crisp, and the internal rhythm stays tight.
Drill 2: KN vs K+N confusion check
Alternate:
K (-.-) then KN (-.–.) then N (-.)
Your goal:
KN feels longer and more “shaped” than either letter alone.
Drill 3: K vs KN meaning drill
Write on paper:
K = anyone reply
KN = called station reply
Then practice sending:
K, KN, KN
So your brain locks the “directed” behavior.