APRS Packet Errors for 443.500AN (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
20260209145912ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209153512ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209161113ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209164712ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209172312ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209175912ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209183513ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209191112ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209194712ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol
20260209202312ESPAN>BEACON,qAR,J73Z-10:;443.500AN*111111z1531.58N/06128.18Wr443.500MHz T103 + R15m Morne Espagnol