APRS Packet Errors for 9M2TEE-15 (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
202602091336099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091406099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091436099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091506099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091536099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091606099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091636099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091706099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091736099M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091806109M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091836109M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS
202602091906109M2TEE-15>APLRG1,TCPIP*,qAC,T2OSAKA:!LMAzqh@$Za GLoRa APRS