APRS Packet Errors for DG2MCM-2 (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
20260208143406DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208150422DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208153437DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208160452DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208163510DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208170525DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208173540DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208180555DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208183614DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208190629DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208193644DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241
20260208200659DG2MCM-2>APRSGW,TCPIP*,qAR,DG2MCM-2:!4743.48N/01019.67E#/B=100/A=002241