APRS Packet Errors for DH2PG-5 (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
20260208165405DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_157/000g...t044p000h78b10065T2WX
20260208182416DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_ 13.5V 23C
20260208184420DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_157/000g...t044p000h79b10069T2WX
20260208194427DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_ 13.5V 23C
20260208194427DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_157/000g...t043p000h80b10067T2WX
20260208205437DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_157/000g...t039p000h83b10070T2WX
20260208211439DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_ 13.5V 22C
20260208212441DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_ 13.5V 23C
20260208212442DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_157/000g...t037p000h84b10069T2WX
20260208220446DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_ 13.5V 22C
20260208220447DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_157/000g...t036p000h86b10071T2WX
20260208222449DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_ 13.5V 22C
20260208222450DH2PG-5>APOT21,WIDE2-2,qAO,DG8JT-2:!5022.21N/00734.65E_157/000g...t037p000h87b10071T2WX