Grid Squares and the Maidenhead Locator System, Explained

Every logbook, every VHF contest exchange and every FT8 handshake carries a string like FN42 or KO26. That string is a Maidenhead grid locator, and it packs your approximate location into four to six characters that any other station on the planet can decode without a lookup table. If you have ever wondered why your rig or your logging software asks for a “grid square” instead of a city name, this is the system behind it, and understanding how it is built makes it far easier to use correctly.

What the Maidenhead Locator System Actually Encodes

The Maidenhead Locator System is a way of dividing the surface of the Earth into a grid of rectangles and giving each rectangle a short alphanumeric code. It was adopted by a group of European VHF operators meeting in Maidenhead, England, in 1980, specifically to solve a practical problem: VHF and UHF operators needed a compact way to state their approximate position so that distance and bearing could be worked out quickly during a contact, without exchanging full coordinates over a weak, fading signal.

Unlike a postal address, a grid locator says nothing about who you are or exactly where your antenna sits. It only describes a rectangle of the Earth’s surface, typically a few kilometres across at the precision most hams use. Two neighbours on the same street will normally share an identical six-character locator, and that is by design — the system was never meant to replace a street address, only to give distance and direction a shorthand.

A Short History: Why “Maidenhead”

The system takes its name from the town where it was formalised in 1980, at a meeting of VHF managers from IARU Region 1 national societies. Before that meeting, several incompatible locator schemes were in informal use across Europe for VHF and UHF work, most notably the older QRA locator system, which made cross-border distance calculation awkward. The Maidenhead scheme was designed to replace those competing formats with a single, internationally agreed grid that any operator, anywhere, could compute from a map or a set of coordinates without needing a lookup table specific to one country. It caught on quickly because it solved a real operational problem rather than being imposed as a standard for its own sake, and within a decade it had effectively become the default locator format worldwide, well beyond its original VHF contesting use case.

How a Grid Square Is Built: Fields, Squares and Subsquares

A full Maidenhead locator is built in layers, each one narrowing down the location further. Reading a locator like KO26FA from left to right walks through those layers in order.

The field (first two letters)

The world is first divided into fields, each identified by two letters from A to R. A field spans 20 degrees of longitude and 10 degrees of latitude, so a single field can cover a large part of a continent. The first letter comes from longitude, the second from latitude. Lithuania, for example, sits inside field KO.

The square (two digits)

Each field is subdivided into 100 squares, numbered 00 through 99, with each square covering 2 degrees of longitude and 1 degree of latitude. This is the resolution most casual references to “your grid” actually mean — four characters, such as KO26, is usually enough to place a station within roughly a hundred kilometres or so, though the exact size varies with latitude because lines of longitude converge toward the poles.

The subsquare (two more letters)

For sharper precision, each square is divided again into 24 by 24 subsquares, lettered a through x, spanning 5 minutes of longitude and 2.5 minutes of latitude. Adding these two letters gives a six-character locator such as KO26FA, which narrows the area down to roughly the size of a small town or a few square kilometres.

Extended precision (rarely needed)

The system can be extended further with a third pair of digits and even a third pair of letters, giving eight- or ten-character locators. These extended forms exist mainly for satellite work, VHF/UHF beacon coordination and a handful of logging tools that want near-GPS precision. For everyday HF and VHF operating, six characters is the practical standard, and four characters is often all that gets exchanged on the air.

Why a Working Ham Actually Needs a Grid Square

VHF and UHF contest exchange

Many VHF and UHF contests, including long-running events organised by national societies, use the four-character grid square as part or all of the contact exchange instead of a conventional signal report. The reason is practical: in VHF and UHF contesting, distance and direction between two grid squares is exactly what determines scoring and what tells an operator which direction to point a beam next. Always confirm the exact exchange format in the current rules of whichever contest you are entering, since requirements do change from year to year and differ between contests and regions.

FT8, FT4 and other digital modes

If you have run WSJT-X for FT8 or FT4, you have already used grid locators without necessarily thinking about it. In the standard, non-contest FT8 message sequence, a station calling CQ transmits their own four-character grid, and the station answering that CQ replies with their own grid in the very first response — signal reports are exchanged only in the messages that follow. That is why WSJT-X asks you to set your grid square correctly before you start operating: an accurate grid is not cosmetic, it is transmitted data that the other station logs.

Distance, bearing, DXCC and award chasing

Grid locators make it trivial for logging software to calculate great-circle distance and bearing between two stations, which is why nearly every modern logging program will show or estimate a contact’s grid even when the operator did not type one in, based on the DXCC entity and general location. For award chasing beyond DXCC — such as grid-square-based VHF awards — an accurate locator in your own station profile and in your log is the entire basis of the award.

Finding Your Own Grid Square

You do not need to calculate your grid locator by hand. The most reliable options, in order of accuracy:

• GPS-based apps or a GPS receiver — the most accurate source, since it uses your actual coordinates rather than an approximate address lookup.
• Your logging or contest software — most programs, including the ones used for FT8 and contesting, include a coordinate-to-grid converter in their setup screen.
• Online grid square calculators — useful for a one-off lookup from an address or coordinates, though double-check the result against a second source if the contact or award depends on it.

Whatever method you use, re-check your grid any time you operate portable — from a POTA park, a contest hilltop, or a friend’s station — since your home grid square is very likely wrong for that location.

Grid Squares for Antenna Aiming and Propagation Planning

Beyond logging and contest exchanges, grid squares are genuinely useful for planning a session before you ever key up. Because a locator converts cleanly to an approximate latitude and longitude, it is the input most propagation and great-circle bearing tools actually want, even when they present it to you as a map. Feed your grid and a target grid into a bearing calculator and you get the short-path heading to point a directional VHF or UHF antenna — a five-minute step that saves a lot of fruitless calling into a dead arc of the compass on a marginal tropospheric or meteor-scatter opening.

The same underlying math is what drives grid-based award tracking: a VHF award built around “worked X number of grid squares” is really just counting how many distinct rectangles you have logged a confirmed contact in, which is why keeping your own configured grid accurate, and reading the other station’s grid correctly, directly affects whether a contact counts toward that kind of award at all.

Grid Square Precision: How Much Detail Do You Need

Common Grid Square Mistakes

A few errors show up repeatedly in logs and on the air:

• Copying someone else’s grid from memory. Two operators a short drive apart can still be in different four-character squares if they straddle a boundary. Never assume a club member shares your grid.
• Forgetting to update it when operating portable. A grid square left set to your home QTH while activating a park or a contest site will quietly corrupt every QSO logged that day.
• Mixing up letter case or digit order. Software generally normalises this automatically, but when typing a grid manually into a contact log, KO26fa and K026FA are easy typos that some strict parsers will reject.
• Treating a grid square as an exact point. It is a rectangle, not a coordinate. Two contacts logged with the same six-character grid are not necessarily at the same address.

Frequently Asked Questions

Is a Maidenhead grid square the same as a postal or ZIP code?

No. Grid squares are defined purely by latitude and longitude bands and have no relationship to postal, administrative or political boundaries. A single grid square can span parts of two countries, and a postal code area can span several grid squares.

How accurate is a six-character grid square?

A six-character locator covers roughly a few square kilometres, which is precise enough for VHF/UHF distance and bearing calculations and for most award programs, but it is not a substitute for GPS coordinates if exact positioning is required.

Do I need to know my grid square for HF operating?

Not usually for casual HF contacts, but it matters the moment you run FT8 or FT4, enter a contest that uses grid as an exchange, or want your log to support distance-based awards, since most digital-mode software and many contest logs expect an accurate grid in your station configuration.

Why does my grid square change slightly between different calculators?

Small discrepancies usually come from rounding of your coordinates or from one tool using your approximate address rather than exact GPS coordinates. If a contact or award depends on precision, use the coordinates from a GPS receiver or phone GPS rather than an address lookup.

Can two stations in the same grid square still calculate a useful distance?

Not meaningfully — if both stations report the same four- or six-character grid, any distance calculation based on grid centres alone will be close to zero even though the two stations may be several kilometres apart. This is a known limitation of grid-based distance tools at short range.

What grid square should I log when operating from a moving vehicle or boat?

Log the grid square for your actual position at the time of each contact, not your starting point. On a long portable or maritime mobile run that crosses grid boundaries, this can mean your grid changes several times in one operating session.

Does the grid square I transmit in FT8 get logged automatically?

Yes — WSJT-X and similar programs log the grid the other station actually transmitted during the QSO, not a value you type in afterward, which is one more reason to make sure your own configured grid is correct before you start a session.

The Bottom Line

The Maidenhead Locator System looks cryptic the first time you see it, but it is really just a compact latitude/longitude shorthand built in three nested layers: field, square and subsquare. Get your own six-character grid right once, keep it updated when you operate portable, and the rest — VHF contest exchanges, FT8 logging, distance and bearing calculations, grid-based awards — takes care of itself. For the full technical definition of field and square boundaries, the Maidenhead Locator System reference on Wikipedia and the ARRL’s grid square guidance are both worth bookmarking alongside your logging software’s own converter.

If your grid-square accuracy matters because you are chasing awards or working toward DXCC, it pairs naturally with the topics in how DXCC actually works and with getting your digital-mode station configured correctly in a WSJT-X and FT8 setup that works the first time. For more station-building and operating articles, browse the full blog index.