APRS Packet Errors for 9W2SPA-2 (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
202602091112029W2SPA-2>APLRG1,TCPIP*,qAC,T2SPAIN:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091136099W2SPA-2>APLRG1,TCPIP*,qAC,T2SPAIN:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091142049W2SPA-2>APLRG1,TCPIP*,qAC,T2SPAIN:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091157049W2SPA-2>APLRG1,TCPIP*,qAC,T2SPAIN:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091441499W2SPA-2>APLRG1,TCPIP*,qAC,T2PERTH:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091456499W2SPA-2>APLRG1,TCPIP*,qAC,T2PERTH:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091511509W2SPA-2>APLRG1,TCPIP*,qAC,T2PERTH:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091526519W2SPA-2>APLRG1,TCPIP*,qAC,T2PERTH:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091541519W2SPA-2>APLRG1,TCPIP*,qAC,T2PERTH:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091556529W2SPA-2>APLRG1,TCPIP*,qAC,T2PERTH:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V
202602091611539W2SPA-2>APLRG1,TCPIP*,qAC,T2PERTH:!LKU/qh>za# GMCG LoRa APRS DG Ext=0.55V