APRS Packet Errors for F1ZFG-13 (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
20260209135346	F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_142/005g000t047r000p000b10060h75Netatmo at the top of the pylon on F1ZFG
20260209145201	F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_149/005g000t048r000p000b10051h73Netatmo at the top of the pylon on F1ZFG
20260209154223	F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_157/006g000t050r000p000b10045h67Netatmo at the top of the pylon on F1ZFG
20260209163449	F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_158/005g000t048r000p000b10044h69Netatmo at the top of the pylon on F1ZFG
20260209172826	F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_159/008g000t046r000p000b10040h73Netatmo at the top of the pylon on F1ZFG
20260209182721	F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_168/011g000t046r000p000b10039h73Netatmo at the top of the pylon on F1ZFG