APRS Packet Errors for M0WTC-15 (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
20250712130757M0WTC-15>APRS,TCPIP*,qAC,SECOND:!5048.41N/0014.53EL using RFinder null
20250712130832M0WTC-15>APRS,TCPIP*,qAC,SECOND:!5048.41N/0014.53EL using RFinder
20250712131025M0WTC-15>APRS,TCPIP*,qAC,FOURTH:!5048.41N/0014.53EL using RFinder
20250712131116M0WTC-15>APRS,TCPIP*,qAC,THIRD:!5048.41N/0014.53EL using RFinder
20250712131235M0WTC-15>APRS,TCPIP*,qAC,SECOND:!5048.41N/0014.53EL using RFinder
20250712131504M0WTC-15>APRS,TCPIP*,qAC,NINTH:!5048.41N/0014.53EL using RFinder
20250712131538M0WTC-15>APRS,TCPIP*,qAC,SECOND:!5048.41N/0014.53EL using RFinder
20250712132013M0WTC-15>APRS,TCPIP*,qAC,THIRD:!5048.41N/0014.53EL using RFinder null
20250712132208M0WTC-15>APRS,TCPIP*,qAC,FOURTH:!5048.41N/0014.53EL using RFinder null
20250712145827M0WTC-15>APRS,TCPIP*,qAC,FIRST:!5048.40N/0014.50EL using RFinder null
20250712150721M0WTC-15>APRS,TCPIP*,qAC,EIGHTH:!5048.40N/0014.50EL using RFinder null