APRS stands for Automatic Packet Reporting System, and it is one of the oldest pieces of digital ham radio still in daily use. Most operators know it as “the thing that puts a dot on a map,” but that undersells it badly. APRS is a real-time, ham-built data network that has been running continuously since before most current hams were licensed, and it still does jobs that newer technology has not fully replaced. This is the long version: where it came from, exactly how a packet gets from your radio to a map on the other side of the country, and everything else worth knowing before you turn it on.

Where APRS Came From

APRS was created by Bob Bruninga, callsign WB4APR, an instructor at the United States Naval Academy. In the mid 1980s Bruninga was experimenting with packet radio for tracking the position of Navy midshipmen during training exercises, and by the late 1980s he had built the first real version of what became APRS, originally standing for Automatic Position Reporting System before the name shifted to reflect its broader use for more than just position data.

The early software ran on DOS and displayed stations as characters on a text-based map, which sounds primitive now but was genuinely novel at the time. Traditional packet radio in the 1980s was built around point-to-point connected sessions, similar in spirit to a phone call, where two stations linked up and exchanged data directly before anything useful happened. Bruninga’s insight was that a lot of useful ham radio data, especially position and status information, did not need a connection at all. It just needed to go out once and be picked up by anyone listening, without a handshake, without an acknowledgment, without tying up the channel with connection overhead. That connectionless, broadcast-style approach is the core idea that makes APRS work the way it does today, and it is what separates APRS from the connected packet BBS networks that came before it.

Through the 1990s, APRS spread as packet TNCs became cheaper and GPS receivers became small and affordable enough to bolt onto a car dashboard. Bruninga kept developing the protocol and the reference software for years, adding weather station support, messaging, and object reporting along the way, and the ham community built compatible clients on top of his open specification rather than everyone being locked into one piece of software. He continued to be the driving force behind APRS until his death in 2022, and the protocol he built is still the standard almost every APRS-capable radio speaks today, more than three decades after the first version went on the air.

The Technical Basics: AX.25 and 1200 Baud

Under the hood, APRS packets ride on AX.25, a packet radio protocol adapted from the wired X.25 standard back in the early days of ham packet radio. Each packet is encoded as audio tones, specifically Bell 202 style AFSK at 1200 baud, the same audio-tone approach used by a lot of older packet radio and some early digital modes. Any FM radio capable of transmitting and receiving that audio can carry APRS, which is exactly why so many handhelds and mobiles have it built in without needing specialized RF hardware.

In North America, APRS traffic runs almost entirely on a single frequency, 144.390 MHz FM. Having one nationwide calling frequency is part of what makes the network work at all. Everyone’s radio is listening in the same place, so a digipeater does not need to guess where to listen, and any APRS-capable station anywhere in range can hear anyone else without retuning. Other regions of the world use different frequencies for the same reason, generally one designated channel per region rather than per country.

What a Digipeater Actually Is

A digipeater, short for digital repeater, is a station that listens for APRS packets and automatically retransmits them, the same basic concept as a voice repeater extending a conversation, except it operates on packets instead of audio and it decides what to repeat based on the routing information embedded in each packet rather than just repeating everything it hears.

Every APRS packet includes a digipeater path, a short list of aliases telling the network how far the packet should travel. The near-universal standard today is WIDE1-1,WIDE2-1. The WIDE1-1 portion is meant to be picked up by a nearby fill-in digipeater, typically a lower power station covering a small area that fills in gaps in terrain coverage. The WIDE2-1 portion is meant for a wide-area digipeater, usually mounted on a hilltop or tower with real coverage, which then relays the packet across a much larger region. Each digipeater that repeats a packet decrements the number after the dash, so a packet only travels two hops total with that path before it stops propagating, which keeps a single transmission from bouncing around a region indefinitely and flooding the frequency.

This two-tier system, a short-range fill-in digipeater feeding into a long-range wide-area digipeater, is deliberate. It means a low-power handheld deep in a valley can still get a packet out through a fill-in station a mile away, which then hands it to a wide-area digipeater on a mountain that covers fifty or a hundred miles, without every single station on the network needing to run high power or a great antenna location. It is a genuinely elegant piece of network design for something built almost entirely by volunteer infrastructure with no central coordinating authority forcing anyone to build anything.

IGates and APRS-IS: How It Went Global

APRS started as a purely RF network, limited by however far a signal could travel through digipeaters. That changed with the arrival of IGates, short for internet gateways, stations that listen for local APRS RF traffic and forward it onto APRS-IS, the internet backbone that ties the whole worldwide network together. A receive-only IGate just listens and uploads; a full IGate can also send messages back down to RF, letting someone on the internet message a station that only has a radio. From APRS-IS, that data lands on tracking sites like aprs.fi, where anyone with a browser can watch stations move in close to real time.

This is the piece that turned APRS from a regional curiosity into something where a station keying up in rural Arizona can be watched from anywhere with an internet connection within seconds. It is also why APRS still has relevance today even though cell phone tracking apps exist for almost everything APRS does on the surface. RF-only APRS keeps working when cell networks and the internet do not, which is exactly the situation where you actually need a tracking and messaging system to hold up. The internet gateway is a convenience layer on top of a network that still functions perfectly well with zero internet connectivity anywhere in the chain.

Callsigns, SSIDs, and Symbols

Every APRS station identifies with its callsign plus an optional SSID, a number from 0 to 15 appended after a dash, used to distinguish multiple stations or device types run by the same operator. There is no hard rule enforced by the network, but a set of informal conventions has developed over the decades: -9 commonly denotes a mobile station, -7 a handheld, -10 a Bluetooth-connected tracker, -13 a weather station, and -0 typically means no SSID was set at all. Using a sensible SSID matters more than it might seem, since anyone looking you up on aprs.fi with multiple devices active benefits from being able to tell at a glance which dot is your car and which one is the handheld in your pocket.

APRS also assigns every station a symbol, a small icon displayed on maps and client software, chosen from a standard symbol table that includes things like a car, a house, a jogging figure, or a weather station icon. Picking a symbol that matches what you actually are helps everyone else on the network make sense of the map at a glance rather than guessing what a random dot represents.

What Actually Rides on APRS

Position beacons get most of the attention, but APRS carries several distinct kinds of data:

  • Position reports, the GPS-derived beacons most people associate with APRS, sent on a timer or through smart beaconing that adjusts frequency based on speed and heading change.
  • Messages, short station-to-station text that works even without cell coverage as long as you are in range of a digipeater or another station, complete with delivery acknowledgment so the sender knows the message actually landed.
  • Weather telemetry, automatically reported by home weather stations, including temperature, wind speed and direction, rainfall, and barometric pressure, feeding into aggregation sites that both hams and outside meteorologists reference.
  • Objects and items, markers placed on the map by any station to represent something that is not itself transmitting, like a repeater location, a shelter, or a net control station during an event.
  • Status and bulletins, free-text broadcasts a station can send about itself or to announce something to everyone in range, often used during nets or public service events.
  • Telemetry, raw numeric data streams used for things like remote sensor readings, which is a less common but still supported piece of the protocol.

Common Uses in the Real World

Beyond the basic tracking and messaging most hams associate with APRS, the network quietly handles a handful of jobs a lot of operators never think about:

  • Race and event support. APRS trackers on support vehicles and lead riders or runners are standard equipment for a lot of ARES and RACES-supported bike races, marathons, and parades, giving net control a live picture of where everyone is without tying up a voice net.
  • SkyWarn and severe weather spotting. Some SkyWarn nets use APRS objects to mark storm reports and rotation sightings on a shared map in addition to voice reports.
  • Satellite operation. The ISS has run an APRS digipeater on and off for years, letting operators bounce a short packet off the space station during a pass, and several amateur CubeSats have carried APRS payloads as well.
  • Repeater and infrastructure status. Clubs use APRS objects to mark a repeater as down or degraded, which shows up automatically on maps operators are already watching.
  • EmComm and served agency support. Objects marking shelters, staging areas, or command posts, alongside messaging that keeps working when phone networks are overloaded or down entirely.
  • DXpedition and special event alerts. Some DXpeditions have used APRS bulletins to broadcast frequency changes or operating schedule updates to anyone monitoring in range.
  • POTA and SOTA activations. A lot of activators beacon their position automatically so hunters and other activators can see who is on the air and roughly where, without needing a separate spotting app.

How APRS Compares to Newer Trackers

Meshtastic, Zello, and similar apps get compared to APRS a lot these days, and they do overlap in purpose, but APRS has one advantage none of them fully match: it has been running, essentially unmodified in its core protocol, for over three decades, with a mature global digipeater and IGate network already built out by other hams. You are not building a mesh from scratch when you turn on APRS. You are joining infrastructure that already exists almost everywhere you are likely to operate. The tradeoff is speed and data richness. APRS moves data at 1200 baud over narrow FM channels, so do not expect it to compete with a LoRa mesh network for throughput or rich data payloads. It was never built for that, and for the specific job of position, status, and short messaging over long distances using infrastructure that already exists, it still does that job extremely well.

A Few Things Worth Knowing Before You Turn It On

APRS traffic is public by design. Every packet you send is visible to anyone monitoring the frequency and, once it hits an IGate, visible to anyone on the internet through aprs.fi. Encryption is not permitted on amateur bands, so do not treat APRS as a private channel for anything sensitive.

It is also a shared, volunteer-built resource. The APRS-IS network runs on unpaid IGate operators, and the RF side runs on a single nationwide frequency shared by everyone in range, so aggressive beacon intervals or unnecessary traffic degrade the system for everyone nearby. A sensible beacon interval, a clean digipeater path like WIDE1-1,WIDE2-1 rather than something longer, and a station that only transmits when it actually has something worth reporting go a long way toward keeping the network usable for the next person who needs it. This is one of those corners of ham radio that runs entirely on good etiquette rather than enforcement, and it has stayed usable for three decades because most operators take that seriously.

Related reading: Setting Up APRS on the Kenwood TH-D75A · Configuring APRS on the AnyTone AT-D878UV II Plus · What Is P25 Digital?


0 0 votes
Article Rating
Subscribe
Notify of
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x
×