APRS Packet Errors for YO3IAZ-1 (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
20250714165503YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E
20250714172505YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E
20250714175506YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E
20250714182508YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E
20250714185510YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E
20250714192512YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E
20250714195514YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E
20250714202516YO3IAZ-1>APRS,qAR,YO3IFO-10:!0000.00S/00000.00WXCristi, MTM800E