APRS Packet Errors for HG6IEP-10 (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
20260209091824HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t039r...p...P...h79b09890LoRa APRS
20260209091829HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t039r...p...P...h79b09890LoRa
20260209111840HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t042r...p...P...h75b09890LoRa APRS
20260209111845HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t042r...p...P...h75b09890LoRa
20260209121849HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t043r...p...P...h74b09890LoRa APRS
20260209121853HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t043r...p...P...h74b09890LoRa
20260209131856HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t044r...p...P...h74b09890LoRa APRS
20260209131901HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t044r...p...P...h74b09890LoRa
20260209141905HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t044r...p...P...h75b09890LoRa APRS
20260209141909HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t044r...p...P...h75b09890LoRa