APRS Packet Errors for XE3WM-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
20260209091940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209094940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209101940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209104940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209111940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209114940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209121940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209124940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209131940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209134940XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209141941XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX
20260209144941XE3WM-10>APLRG1,TCPIP*,qAC,T2ROMANIA:!LCrrd7mm"a GLoRa APRS IGATE MERIDA MX