APRS Packet Errors for b0sda (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
20260927220105b0sda>APRS,TCPIPC,FT,qAR,AE7AF:;P6F22201z50N0043H101APNET POC ransmi147INE
20260928000035b0sda>APRS,TCC,SECOND,qAR,AE7AF:;P-N7Ez465352W#PT POCmitter(04IE)
20260928000218b0sda>APRS,TCPIP*,COND,qAR,AE7AF:;P1*280002z4918.85NP0G0000DG TsiF)NLINE)RGSTRY>P*,qAC,T2RDU:ping{
20260928000315b0sda>ND,qAR,AE7AF:;P-DO4SA003z49P43E#PHGET POCSAG Trer
20260928020040b0sda>APRS,TAC,TH,qAR,AE7AF:;K6AB28023.58PPHG0120ransmitter(ONE)
20260928030023b0sda>APRS,TCPIH,qAR,AE7AF:;AX 122N0949E#PHGOCSnsmter)(O)
20260928030129b0sda>APNTH,qAR,AE7AF:;P-DBB *200808.17E#0000DAPNET POCSAG itter(LINE)