APRS Packet Errors for OE8XXX-7 (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
20240329081321OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAU,OE1XUR-10:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329081733OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAS,OE3KJN-10:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329082100OE8XXX-7>APDR10,OE6XTR,OK0EK-3,WIDE2*,qAR,OK2VOP-1:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329082138OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAU,OE1XUR-10:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329082541OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAR,OE1IWA-12:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329082944OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAR,OE1IWA-12:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329083125OE8XXX-7>APDR10,OE6XTR*,WIDE2-1,qAR,OK2VOP-1:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329083130OE8XXX-7>APDR10,OE6XTR,OK2VOP-1*,qAR,OK2KOJ-1:!0000.00N/00000.00E[/A=000000OE8XXX SeppliYƒ
20240329083350OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAR,OE1IWA-12:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329083755OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAR,OE1IWA-12:!0000.00N/00000.00E[/A=000000OE8XXX Seppli
20240329084158OE8XXX-7>APDR10,WIDE1-1,WIDE2-1,qAR,OE1IWA-12:!0000.00N/00000.00E[/A=000000OE8XXX Seppli