APRS Packet Errors for DO2ZZ-12 (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
20260209150252DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209153307DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209160322DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209163340DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209170355DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209173410DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209180425DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209183443DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209190458DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209193510DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663
20260209200525DO2ZZ-12>APRSGW,TCPIP*,qAR,DO2ZZ-12:!4813.93N/00955.94E#MeshCom-Gate Burgrieden/B=100/A=001663