Knowledge · Guide
What's the difference between NMEA 0183 and NMEA 2000?
NMEA 0183 sends data as readable text in “sentences” with three-letter names, such as RMC. NMEA 2000 sends the same information in binary, in numbered packets called PGNs, such as 129025. NMEA 2000 is faster, networks many devices over one shared cable, and carries data that doesn't exist in NMEA 0183, like tank levels and engine hours.
Updated: November 2026
The two protocols differ fundamentally: in how data is transmitted, and in how it's labeled. This article explains both differences using a concrete example.
Terms in this article (8)
- NMEA
- National Marine Electronics Association. The US trade association of marine electronics manufacturers that publishes both standards.
- NMEA 0183
- The older standard, from 1983.
- NMEA 2000
- Its successor, often shortened to “N2K.
- Sentence
- One line of text in NMEA 0183 with a three-letter name, such as RMC for “Recommended Minimum Navigation Information.”
- PGN
- Parameter Group Number. The number that identifies a data packet in NMEA 2000.
- ASCII
- American Standard Code for Information Interchange. The table that assigns a number to every letter and digit so that text can be transmitted.
- CAN bus
- Controller Area Network. A data bus from the automotive industry that NMEA 2000 is built on: all devices hang off one shared cable.
- Signal K
- An open data format for boats that makes data from both NMEA standards available on the network in one consistent format.
At a glance
| NMEA 0183 | NMEA 2000 | |
|---|---|---|
| Transmission | Text (ASCII) | Binary |
| How data is labeled | Sentence with three letters, e.g., RMC | PGN, a number, e.g., 129025 |
| Wiring | One talker per line, several listeners | Shared bus (CAN), all devices send and receive |
| Speed | 4,800 bps, or 38,400 bps at high speed | 250,000 bps |
| Position per second | Usually once | Up to ten times |
| Engine, tanks, batteries | Only via workarounds (XDR) | Dedicated PGNs |
| In the Logbook app | 26 sentences | 22 PGNs |
NMEA 0183 transmits all data as human-readable text characters (letters A–Z, digits 0–9, and a few punctuation marks and special characters), which are encoded into a binary format for transmission. NMEA 2000 transmits the data directly in binary. On top of that, the protocol itself, meaning how the data is put together and how it's labeled, is different.
The difference in how data is transmitted
Say the number 213 needs to be transmitted. In NMEA 0183, the three digits (that is, characters) 2, 1, and 3 go over the bus in binary, but encoded in ASCII:
In ASCII, the character 2 is the number 50 in decimal, which is 00110010 in binary. So those 8 bits are sent for the character 2.
The same goes for the other characters: 1 → 49 → 00110001 and 3 → 51 → 00110011. That makes three times 8 bits to transmit:
00110010 + 00110001 + 00110011If 213 is transmitted in NMEA 2000, on the other hand, the number 213 is converted straight to 11010101 in binary, so only 8 bits are sent. That's faster because there's less to transmit, and because NMEA 2000 transmits data at a higher speed. As a result, updates such as the position no longer hit the bus just once per second but ten times per second.
The difference in how data is labeled (metadata)
The standardized values in NMEA 0183 are called NMEA sentences; they consist of three letters. In NMEA 2000, it's a number called a PGN. One very common sentence and PGN is the one for the current GPS position.
Example
Each has its own protocol for how this data is put together. The position as an NMEA 0183 sentence is, for example, the following NMEA sentence with the three letters “RMC” (source):
$GPRMC,133848.725,A,5413.480,N,00759.811,E,,,120826,000.0,W*7CIts counterpart containing the position data in NMEA 2000 is PGN 129025 (source). In binary it consists of nothing but zeros and ones; shown in hexadecimal so humans can read it, it looks like this:
A052402.340 0FFF2 1F801 DB065220C438C404Both data records hold the same latitude and longitude as position information:
- Latitude: 54.22466191°
- Longitude: 7.99684524°
And here's how differently it gets converted:
| NMEA 0183 for the RMC sentence | Latitude | Longitude |
|---|---|---|
| In decimal | 54.22466191° | 7.99684524° |
| In degrees and decimal minutes | 54° 13.4797′ | 7° 59.8107144′ |
| Rounded | 54° 13.480′ | 7° 59.811′ |
| As it appears in the NMEA 0183 data record, which is then transmitted as ASCII-encoded text | 5413.480 | 759.811 |
| NMEA 2000 for PGN 129025 | Latitude | Longitude |
|---|---|---|
| In decimal | 54.22466191° | 7.99684524° |
| Multiplied by 10000000 (ten million) | 542246619.1 | 79968452.4 |
| After rounding we have a whole number that always fits into a 32-bit data field and is transmitted that way in the NMEA 2000 data record | 542246619 | 79968452 |
| For illustration, the value in hexadecimal | 205206DB | 04C438C4 |
| To match the representation above, the byte order still has to be reversed | DB065220 | C438C404 |
| The value as transmitted in binary on the bus | 11011011000001100101001000100000 | 11000100001110001100010000000100 |
For the sake of completeness: according to the specification, PGN 129025 is transmitted ten times per second (every 100 ms). There's another PGN for position data, PGN 129029, but it's only transmitted once per second.
And what is Signal K?
Signal K isn't a third cable on board; it's an open data format for the network. A Signal K server, usually on a Raspberry Pi, reads in NMEA 0183 and NMEA 2000 and makes all the values available over Wi-Fi in one consistent format: as readable JSON, with descriptive names and fixed units.
The same position looks like this in Signal K:
{"path": "navigation.position", "value": {"latitude": 54.22466191, "longitude": 7.99684524}}| NMEA 0183 | NMEA 2000 | Signal K | |
|---|---|---|---|
| Position is called | RMC | PGN 129025 | navigation.position |
| Format | Text | Binary | JSON |
| Lives on | Serial line | CAN bus | Wi-Fi / network |
| License | Paid standard | Paid standard | Open and free |
How to connect a Signal K server to the app is covered in the guide Connect Signal K to the Logbook app.
Using it in the Logbook app
The Logbook app reads all three: NMEA 0183, NMEA 2000, and Signal K. It detects the format on its own, so you don't have to change any settings. Mixed data over one connection isn't a problem either.
NMEA 2000 has data records that NMEA 0183 doesn't know. Among others, the app uses these:
- Engine hours (PGN 127489) and engine RPM (PGN 127488)
- Battery voltage (PGN 127508) and state of charge (PGN 127506)
- Tank contents for fuel, fresh water, gray water, and black water (PGN 127505)
The app reads these PGNs directly. Your gateway doesn't have to convert them to NMEA 0183, and you don't have to configure anything by hand. How to get the values into your logbook is covered in the guide Engine, tanks, and batteries over NMEA 2000.
Since a phone has no port for NMEA cables, you need a gateway that puts the data on Wi-Fi. Connect NMEA over Wi-Fi shows which devices can do that and how to set them up.
Frequently asked questions
What's the difference between NMEA 0183 and NMEA 2000?
NMEA 0183 sends data as readable text in sentences with three-letter names, such as RMC. NMEA 2000 sends the same information in binary, in numbered packets called PGNs, such as 129025. NMEA 2000 is faster, networks many devices over one shared bus, and carries additional data like tank levels and engine hours.
Is NMEA 2000 better than NMEA 0183?
NMEA 2000 is faster, easier to wire, and carries more kinds of data, such as engine and tank data. NMEA 0183, on the other hand, is simple, readable, and available on almost every older device. For your logbook, both deliver the same navigation data.
Are NMEA 0183 and NMEA 2000 compatible?
Not directly. Connectors, wiring, and data format are different. A gateway or converter translates between the two.
What is a PGN?
PGN stands for Parameter Group Number. In NMEA 2000, the number identifies a group of related data, the same way the three letters identify a sentence in NMEA 0183. PGN 129025, for example, contains the position.
Can the Logbook app read NMEA 0183 and NMEA 2000 at the same time?
Yes. Both formats can arrive mixed over one connection. The app recognizes each data record on its own.
Is SeaTalk the same as NMEA?
No. SeaTalk 1 is a proprietary Raymarine protocol. SeaTalk NG, on the other hand, is electrically NMEA 2000 with different connectors and can be hooked up to an NMEA 2000 gateway with an adapter cable.