APRS Packet Errors for DM0BGH-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
20260209132014DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209135014DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209142014DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209145014DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209152015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209155015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209162015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209165015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209172015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209175015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209182015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568
20260209185015DM0BGH-12>APRSGW,TCPIP*,qAR,DM0BGH-12:!4810.62N/01250.26E-located DF0EG/B=100/A=001568