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
20260208151338	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t046h93b09935LoRa APRS
20260208154338	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t046h92b09934LoRa APRS
20260208161338	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t046h91b09934LoRa APRS
20260208164339	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h92b09934LoRa APRS
20260208171339	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h94b09934LoRa APRS
20260208174339	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h95b09934LoRa APRS
20260208181339	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h95b09934LoRa APRS
20260208184339	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h96b09934LoRa APRS
20260208191340	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h96b09933LoRa APRS
20260208194340	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h96b09933LoRa APRS
20260208201340	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h96b09934LoRa APRS
20260208204340	M0SDM-10>APLRG1,TCPIP,qAC,T2POLNW:!L3dtQN>#_ G.../...g...t045h96b09932LoRa APRS