APRS Packet Errors for DG1FBA-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
20260209130040DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209133058DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209140113DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209143128DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209150143DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209153201DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209160216DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209163231DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209170246DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209173305DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209180320DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010
20260209183335DG1FBA-12>APRSGW,TCPIP*,qAR,DG1FBA-12:!5027.70N/00756.87E#/B=100/A=001010