APRS Packet Errors for DD8XX-12 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20260209092510DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209095525DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209102540DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=072/A=002379
20260209105558DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209112613DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209115628DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209122643DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209125701DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209132716DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209135731DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209142746DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=100/A=002379
20260209145758DD8XX-12>APRSGW,TCPIP*,qAR,DD8XX-12:!4729.07N/01107.09E&MESHCOM IGate/B=042/A=002379