APRS Packet Errors for TA2VG-12 (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
20250915152015TA2VG-12>APLIGA,TCPIP*,qAC,T2DENMARK:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915160018TA2VG-12>APLIGA,TCPIP*,qAC,T2SYDNEY:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915161434TA2VG-12>APLIGA,TCPIP*,qAC,T2UKRAINE:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915165434TA2VG-12>APLIGA,TCPIP*,qAC,T2LUBLIN:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915173437TA2VG-12>APLIGA,TCPIP*,qAC,T2TAS:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915174810TA2VG-12>APLIGA,TCPIP*,qAC,T2SPAIN:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915180810TA2VG-12>APLIGA,TCPIP*,qAC,T2SPAIN:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915182811TA2VG-12>APLIGA,TCPIP*,qAC,T2TAS:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915190811TA2VG-12>APLIGA,TCPIP*,qAC,T2DENMARK:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915193219TA2VG-12>APLIGA,TCPIP*,qAC,T2FINLAND:!0 0.00NL00 0.00E& LoRa APRS iGate
20250915201220TA2VG-12>APLIGA,TCPIP*,qAC,T2TAS:!0 0.00NL00 0.00E& LoRa APRS iGate