APRS Packet Errors for DG0SD-10 (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
20260209130551	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091305z5411.30N/01208.38E_000/000g000t034r000p000P000h85b10123
20260209134706	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091346z5411.30N/01208.38E_000/000g000t033r000p000P000h86b10121
20260209142421	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091424z5411.30N/01208.38E_000/000g000t033r000p000P000h87b10118
20260209150726	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091507z5411.30N/01208.38E_000/000g000t033r000p000P000h87b10116
20260209154414	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091543z5411.30N/01208.38E_000/000g000t032r000p000P000h88b10114
20260209162851	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091628z5411.30N/01208.38E_000/000g000t032r000p000P000h89b10113
20260209170631	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091705z5411.30N/01208.38E_000/000g000t032r000p000P000h90b10108
20260209174246	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091742z5411.30N/01208.38E_000/000g000t032r000p000P000h91b10107
20260209182711	DG0SD-10>APRX29,TCPIP*,qAC,T2PERTH:@091826z5411.30N/01208.38E_000/000g000t032r000p000P000h91b10105