APRS Packet Errors for DK2FK-3 (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
20260209115034DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=100/A=001660
20260209122049DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=100/A=001660
20260209125104DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=100/A=001660
20260209132121DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=100/A=001660
20260209135136DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=100/A=001660
20260209142151DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=100/A=001660
20260209145206DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=099/A=001660
20260209152225DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=099/A=001660
20260209155240DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=099/A=001660
20260209162255DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=099/A=001660
20260209165310DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=099/A=001660
20260209172329DK2FK-3>APRSGW,TCPIP*,qAR,DK2FK-3:!4818.43N1009.57ELMeshCom/B=091/A=001660