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
20260208181615HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t041r...p...P...h81b09860LoRa APRS
20260208181619HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t041r...p...P...h81b09860LoRa APRSPRSPRSP
20260208191623HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t041r...p...P...h81b09860LoRa APRS
20260208191628HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t041r...p...P...h81b09860LoRa APRSPRSPRSP
20260208211640HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t040r...p...P...h81b09870LoRa APRS
20260208211645HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t040r...p...P...h81b09870LoRa APRSPRSPRSP
20260208221648HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t040r...p...P...h81b09870LoRa APRS
20260208221653HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t040r...p...P...h81b09870LoRa APRSPRSPRSP
20260208231657HG6IEP-10>APLRG1,WIDE1-1,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t040r...p...P...h81b09870LoRa APRS
20260208231701HG6IEP-10>APLRG1,HG6IEP-10*,qAR,HA9OZD-17:=4802.92NL02009.17E_.../...g...t040r...p...P...h81b09870LoRa APRSPRSPRSP