APRS — short for Automatic Packet Reporting System — is a real-time digital communications protocol used by licensed amateur radio operators worldwide. It carries short bursts of data — your position, the weather around you, telemetry from a balloon, a quick text message — over the same VHF and HF bands hams have used for voice for decades. If you have ever seen a live map of moving stations and weather sensors at aprs.fi or on the live map at the aprs.world homepage, you have already seen APRS in action.
This guide is the cornerstone of our APRS fundamentals cluster. It explains what APRS is, where it came from, how a single beacon transmitted from a car's roof ends up on a website seconds later, what kinds of data the network carries, who actually uses it, and how a brand-new ham can get on the air for the first time.
APRS is a one-to-many, packet-switched digital protocol layered on top of AX.25, the standard ham-radio packet link layer. Every packet is a short, self-contained unit — typically well under 256 bytes — that any receiver in range can decode. There is no session, no login, no handshake. A station "beacons" its data on a schedule, anyone listening on the same frequency can pick it up, and a worldwide volunteer network of repeaters and gateways forwards a copy to the public APRS-IS internet backbone. From there it lands on websites, phone apps, and other radios within seconds.
The name was originally written Automatic Position Reporting System when Bob Bruninga (WB4APR) first published the idea in the late 1980s, but Bruninga himself revised it to the broader Automatic Packet Reporting System because position is only one of the things APRS carries. The "P" in APRS is for "packet", not "position".
APRS was created by Bob Bruninga, an instructor at the U.S. Naval Academy, starting in the late 1980s and reaching its first widely distributed software release in 1992. Bruninga's original goal was to share tactical situational awareness — the live positions of stations participating in a public-service event such as a marathon or a sailing regatta — across a small group of radios.
The first APRS implementation ran on Apple II hardware and used a paper map with a transparent overlay; over the next decade it migrated to MS-DOS, Windows, and eventually open-source clients on Linux, macOS, Android, and iOS. The APRS protocol specification version 1.0.1 — "APRS101.PDF" — was published in 2000, and Bruninga went on maintaining protocol addenda on aprs.org right up to his passing in 2022.
Those corrections were never merged back into the 2000 document, which is why APRS101.PDF on its own is no longer a safe basis for writing an APRS implementation — a client built from it will be out of step with what the network actually does today. The reference to work from is the APRS Protocol Reference version 1.2, an independent compilation by John Langner WB2OSZ that merges the original specification with the relevant corrections and additions published since 2000. It is careful to describe itself as unofficial — the APRS Working Group's formal position is still APRS101.PDF plus Bruninga's separate errata — but as a practical matter it is the one document that has the current behaviour in one place. Chapter numbers in these guides refer to version 1.2.
Although the protocol has had only minor formal updates since then, the network around it has grown enormously. The public APRS-IS backbone — the Internet routing tier that ties every regional radio network together — now carries packets from tens of thousands of distinct stations on any given day.
Understanding the data flow is the single most useful mental model for APRS. A packet's journey from a moving car to a webpage involves four layers:
The RF beacon. Your radio (or a phone with a TNC, or a tracker board such as a Tiny Track or LightAPRS) transmits a short burst of audio-frequency-shift-keyed data on the local APRS frequency. In most of IARU Region 2 (the Americas) that frequency is 144.390 MHz; in Region 1 (Europe and Africa) it is 144.800 MHz; Region 3 (Asia-Pacific) varies by country. We cover this in detail in our APRS frequencies by country guide.
The digipeater (digi). Other amateur stations running digipeater software hear the packet, check its path (a list of "hops" the originator allowed), and rebroadcast it once on the same frequency so distant stations can hear it too. The modern recommended path on VHF is WIDE1-1,WIDE2-1, which gives a beacon up to two hops — usually enough to reach the nearest internet gateway without flooding the channel.
The iGate (Internet gateway). A receiver with an Internet connection — usually a Linux box running aprx or Direwolf, sometimes but not necessarily also a digipeater — uploads the packets it decodes to APRS-IS over TCP. Not everything gets forwarded: packets marked NOGATE or RFONLY must stay on RF. The iGate authenticates with a free, callsign-derived passcode, not a password.
APRS-IS. The Automatic Packet Reporting System Internet Service is a worldwide mesh of around a dozen Tier 2 servers that share every packet they receive with each other in real time. Anyone — a website, a phone app, a researcher — can connect to a Tier 2 server, optionally apply a server-side filter (only my callsign, only stations within 50 km of this point), and receive a live stream of packets matching the filter.
The whole journey from your microphone PTT to a marker appearing on a public website typically takes one to three seconds.
Although APRS is best known for moving-vehicle tracking, the protocol defines a much wider menu of data types:
Each packet's data type is identified by a single ASCII byte at the start of the information field — ! and = for positions, ; for objects, : for messages, and so on. The full table lives in APRS Spec 1.2, chapter 5.
APRS attracts a surprisingly diverse user base, all under one umbrella of a valid amateur radio license:
Country and regional clubs also organise periodic local nets — for example, the TR APRS Çevrim Friday net in Turkey, or the United States APRSSIG discussion list — to keep the community organised.
APRS is one of the most beginner-friendly digital modes in amateur radio because the cost of entry is low and the feedback loop (you appear on a public website within seconds of pressing PTT) is immediate.
You need a valid amateur radio licence in your country to legally transmit APRS. Most countries license at three or four levels; even the entry-level ticket — Technician in the U.S., Foundation in the U.K., A-class in Turkey — gives you full VHF privileges, which is everything APRS needs. Take a class with your local club and pass the multiple-choice exam. The cost is usually nominal.
There are roughly four common paths into APRS:
We have a more detailed buyer's guide on the APRS hardware page.
To upload your packets to APRS-IS (or to log into web tools that authenticate you), you need a free numeric passcode derived from your callsign. It is not a password and not a security token — it is more like a courtesy filter that proves you can read the algorithm. We explain it fully in the APRS passcode guide.
Set your callsign, pick an appropriate APRS symbol (a car for mobile, a house for home, a balloon for high-altitude experiments), enter the local frequency from our country reference table, and press beacon. Within seconds you should appear on aprs.fi, on the aprs.world live map, or on whichever client your friends use.
"APRS uses GPS, so it must be a GPS thing."
It is not. APRS is a transport protocol; GPS is one of many sources that can feed a position into a beacon. Plenty of stations beacon a fixed home location with no GPS at all. Plenty of others beacon a Maidenhead grid that they typed in by hand.
"APRS is encrypted, so my conversations are private."
The opposite. Amateur radio in nearly every jurisdiction is forbidden from using encryption (with very narrow exceptions for command-and-control of satellites). Every APRS packet is in the clear and is by design public. Treat it like a public Twitter feed.
"I need an iGate at home or my packets will not reach the Internet."
You almost never do. The volunteer iGate network is dense in most populated areas. As long as you give your beacon a reasonable path — WIDE1-1,WIDE2-1 is the modern default — somebody else's iGate will pick it up.
"APRS is dying."
Not really — on a typical day in mid-2026 our own APRS-IS feed logs more than 60,000 unique callsigns beaconing worldwide (the 30,000 figure still quoted in places is roughly two decades old). The protocol is stable and well-understood, which means there is little new to write about it from a protocol standpoint, but the user community continues to expand into balloons, IoT, and emergency-comms experiments.
Do I need internet to use APRS? No. RF-only networks work fine for local groups; the Internet (APRS-IS) tier is purely an optional convenience for global visibility.
How fast is the data? The standard VHF link is 1,200 baud — slow by Internet standards, very fast by ham-radio standards. HF APRS runs at 300 baud. Newer experiments such as Wisp APRS over LoRa achieve different trade-offs.
Can I use APRS for chat? Yes — short text messaging works between any two callsign-addressable stations and across APRS-IS. It is not a chatroom protocol though; longer conversations should move to voice or to a digital voice mode.
Where do I see my packets? aprs.fi, aprs.world, and most amateur radio club websites stream APRS-IS packets onto a map. Click your own callsign to see your tracking history.
Is APRS the same as packet radio? APRS is one specific application of packet radio. Generic packet radio (BBS, mailbox systems, TCP/IP over AX.25) is a much older, broader category that mostly faded with the rise of the Internet; APRS survived because it solved a problem the Internet did not address well: real-time situational awareness over RF.
If this is your first encounter with APRS, the natural follow-up reading is:
Welcome to APRS. The map awaits.