APRS Packet Errors for DB0KT-11 (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
20260208194623DB0KT-11>APRSMC,TCPIP*,qAR,DG3FAW-12:!5029.20N/00916.49E#/B=100/A=002372
20260208201628DB0KT-11>APRSMC,TCPIP*,qAR,DH1TZ-12:!5029.20N/00916.49E#/B=100/A=002451
20260208204640DB0KT-11>APRSMC,TCPIP*,qAR,DG3FAW-12:!5029.19N/00916.48E#/B=100/A=002484
20260208211627DB0KT-11>APRSMC,TCPIP*,qAR,DG3FAW-12:!5029.21N/00916.49E#/B=100/A=002415
20260208214709DB0KT-11>APRSMC,TCPIP*,qAR,DG3FAW-12:!5029.21N/00916.49E#/B=100/A=002375
20260208221636DB0KT-11>APRSMC,TCPIP*,qAR,DH1TZ-12:!5029.18N/00916.48E#/B=100/A=002572
20260208224623DB0KT-11>APRSMC,TCPIP*,qAR,DL1ZP-12:!5029.18N/00916.49E#/B=100/A=002480
20260208231624DB0KT-11>APRSMC,TCPIP*,qAR,DH1TZ-12:!5029.20N/00916.49E#/B=100/A=002431
20260208231758DB0KT-11>APRSMC,TCPIP*,qAR,DF7ZI-1:!5029.20N/00916.49E#/B=100/A=002431
20260208234626DB0KT-11>APRSMC,TCPIP*,qAR,DH1TZ-12:!5029.20N/00916.49E#/B=100/A=002395
20260209001624DB0KT-11>APRSMC,TCPIP*,qAR,DH1TZ-12:!5029.21N/00916.49E#/B=100/A=002310
20260209011636DB0KT-11>APRSMC,TCPIP*,qAR,DG3FAW-12:!5029.17N/00916.53E#/B=100/A=002310