APRS Packet Errors for OE3MTC-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
20260208164803OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XOC-12:!4819.78N/01613.27E#/B=100/A=000607
20260208171803OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XPA-12:!4819.78N/01613.27E#/A=000607
20260208174803OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XPA-12:!4819.78N/01613.27E#/B=100/A=000607
20260208181808OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XIR-12:!4819.78N/01613.27E#/B=100/A=000607
20260208184803OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XWJ-12:!4819.78N/01613.27E#/B=100/A=000607
20260208191805OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XOC-12:!4819.78N/01613.27E#/B=100/A=000607
20260208194811OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XOC-12:!4819.78N/01613.27E#/B=100/A=000607
20260208201803OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XOC-12:!4819.78N/01613.27E#/B=100/A=000607
20260208204813OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XOC-12:!4819.78N/01613.27E#/B=100/A=000607
20260208211810OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XWJ-12:!4819.78N/01613.27E#/B=100/A=000607
20260208214827OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XOC-12:!4819.78N/01613.27E#/B=006/A=000607
20260208221804OE3MTC-10>APRSMC,TCPIP*,qAR,OE3XOC-12:!4819.78N/01613.27E#/B=100/A=000607