APRS Packet Errors for SP6DL-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
20260208163712SP6DL-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208163717SP6DL-10>APLRG1,SP6NIP-10*,qAR,SP6BVK-10:=L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208165213SP6DL-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208170713SP6DL-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208172213SP6DL-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208172217SP6DL-10>APLRG1,SP6NIP-10*,qAR,SP6BVK-10:=L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208173713SP6DL-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208173717SP6DL-10>APLRG1,SP6NIP-10*,qAR,SP6BVK-10:=L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208175213SP6DL-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208175217SP6DL-10>APLRG1,SP6NIP-10*,qAR,SP6BVK-10:=L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208180713SP6DL-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST
20260208204416SP6DL-10>APLRG1,TCPIP*,qAC,T2SWEDEN:!L4X?DRUS## !GLoRa APRS 434.855MHz TEST