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
20260208204445F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_314/003g000t037r000p000b10073h96Netatmo at the top of the pylon on F1ZFG
20260208214156F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_297/003g000t036r000p000b10074h96Netatmo at the top of the pylon on F1ZFG
20260208223121F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_298/002g000t036r000p000b10076h94Netatmo at the top of the pylon on F1ZFG
20260208232209F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_221/001g000t036r000p000b10078h94Netatmo at the top of the pylon on F1ZFG
20260209001606F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_129/001g000t034r000p000b10078h96Netatmo at the top of the pylon on F1ZFG
20260209011556F1ZFG-13>APRX29,DIRECT,TCPIP*,qAS,F1ZFG:!4549.39N/00449.21E_143/001g000t035r000p000b10079h96Netatmo at the top of the pylon on F1ZFG