APRS Packet Errors for d0sda (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
20260925010011	d0sda>APRS,TCPIqAC,TH,qAR,AE7AF:;P-R1G *250z6943325.5PHG112PNEmitter(ONLIN
20260925010110	d0sda>APRS,TCPIP,qAS,AE7AF:;P-2501.19NP0W#PHG0Transe(048C)(ONLINE)
20260925020150	d0sda>APRS,TCPIP,qAS,AE7AF:;P-NGT2 2z1817.P06707W#PHG10APNET POCSAGansmer(6)(ONLINE)
20260925020201	d0sda>APRS,TCPAC,FIFTH,qAR,AE7AF:;PTR 6.68NP00618ET POCransmi1A)(ONLI
20260925030033	d0sda>APCPIPFTH,qAR,AE7AF:;P-0300z474N3E#PNET POCSAG TaLNE)
20260925030224	d0sda>APTCIA,FIFTH,qAR,AE7AF:;B3YES 0302z4.28NP00733.#PHG1-DAPNETG Trmitter6789AB)