APRS Packet Errors for M0SDM-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
20260209161351	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t046h94b09872LoRa APRS
20260209164351	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t046h95b09869LoRa APRS
20260209171352	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t046h96b09868LoRa APRS
20260209174352	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h95b09867LoRa APRS
20260209181352	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h95b09865LoRa APRS
20260209184352	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h95b09865LoRa APRS
20260209191353	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h95b09864LoRa APRS
20260209194353	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h95b09862LoRa APRS
20260209201354	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h94b09860LoRa APRS
20260209204354	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t044h94b09858LoRa APRS
20260209211354	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t044h94b09858LoRa APRS
20260209214354	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t044h94b09855LoRa APRS