APRS Packet Errors for OE8DKR-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
20250111144624OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[181/000/A=000000OE8DKR
20250111144825OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[181/000/A=000000OE8DKR
20250111145030OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[206/000/A=000000OE8DKR
20250111152837OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[214/000/A=000000OE8DKR
20250111153101OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[015/000/A=000000OE8DKR
20250111153905OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[/A=000000OE8DKR
20250111154145OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[132/000/A=000000OE8DKR
20250111154346OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[226/002/A=000000OE8DKR
20250111154904OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[206/001/A=000000OE8DKR