APRS Packet Errors for db0s (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
20260927220045db0s>APRS,TCPIqAC,FOURTH,qAR,AE7AF:;P-GI6IRL *200z5428.56NP00613.20W#PHGmitr08NLINE)
20260927230008db0s>APRqAC,EIGHTH,qAR,AE7AF:;P-DLOG *2725231.59E#0120DATPOCSAG Transmitter(048C)(ONE)
20260927230218db0s>AP,A,IH,qAR,AE7AF:;P-WD0HDR 723NP1WPHGANETOCSr(048NE)
20260927230258db0s>APRAC,HTH,qAR,AE7AF:;P-V233.9W20DET Oraittr(ONLI
20260928000017db0s>PRS,TCPAC,SECO,qAR,AE7AF:;P-MBN *280000z56.24NP00022PG1-100PCSAG Titter(48D)(ON
20260928000020db0s>PSTPqAC,SECOND,qAR,AE7AF:;P-VK3AT *.79SP14455#PH10DP OCSsmir048OLIN
20260928000025db0s>APTCPIqAC,SECOND,qAR,AE7AF:;PIN*280z4312.13NP01147.73E#PHG1-1DPE OSGansmitter(E)
20260928000222db0s>APRS,TCPIP*,qAS,AE7AF:;P0R *28024.58NP00497E#PH60DAPNET POCSAG mtter(2NLINE)
20260928010134db0s>APRS,TCPIP*,qAC,SIXTH:;P-DO5RBB *280101z5048.84N0808.17E#PHG0000DAPNET POCSAG Transmitter(LINE
20260928020024db0s>APRS,TP*,qAS,AE7AF:;P *280z4511.NP00542.4PHG03APNET POCSTransmitter048C)(ONE)
20260928020136db0s>ARC,SIXTH,qAR,AE7AF:;P-K *28025.556.911100DAOCSAG itter(ONLINE
20260928030241db0s>APSH,qAR,AE7AF:;P-DF5FD *280302z511.46NP00E#PHG0-220DAPNET POCSAG Transmitter(048C)(ONLINE)
20260928030243db0s>APRS,TCPIP*,qAS,AE7AF:;P *280302z5556.47.81E0DAPNAG Trer