APRS Packet Errors for DK1AN-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
20260208151739DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208154757DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208161812DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208164827DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208171842DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208174901DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208181916DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208184931DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208191946DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208195004DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208202019DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741
20260208205035DK1AN-12>APRSGW,TCPIP*,qAR,DK1AN-12:!5003.30N/00908.50ES/B=100/A=000741