APRS Packet Errors for HS5MOA-4 (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
20260209104951HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209112013HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209115035HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209122057HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209125119HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209132140HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209135202HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209142224HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209145246HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209152308HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209155330HS5MOA-4>AESPG4,TCPIP*,qAC,T2OSAKA:=1819.28N/09930.71ErIndy Igate Lampang
20260209155532HS5MOA-4>AESPG4,TCPIP*,qAC,T2HAKATA:=1819.28N/09930.71ErIndy Igate Lampang
20260209162554HS5MOA-4>AESPG4,TCPIP*,qAC,T2HAKATA:=1819.28N/09930.71ErIndy Igate Lampang