APRS Packet Errors for DG3MGG-30 (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
20260208162353DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=019/A=002418
20260208165406DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=033/A=002418
20260208172421DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=047/A=002418
20260208175436DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=048/A=002418
20260208182451DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=013/A=002418
20260208192525DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=041/A=002418
20260208195536DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=013/A=002418
20260208202554DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=031/A=002418
20260208205604DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=036/A=002418
20260208212619DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=042/A=002418
20260208215634DG3MGG-30>APRSMC,TCPIP*,qAR,DG3MGG-12:!4743.67N/01111.44E#/B=035/A=002418