APRS Packet Errors for OE8DKR-7 (last 24 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
20250508134751OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[/A=000000OE8DKR
20250508135344OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[233/000/A=000000OE8DKR
20250508135547OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[118/051/A=000000OE8DKR
20250508135749OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[102/060/A=000000OE8DKR
20250508140955OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[339/030/A=000000OE8DKR
20250508141156OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[017/020/A=000000OE8DKR
20250508144833OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[082/000/A=000000OE8DKR
20250508145035OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[082/000/A=000000OE8DKR
20250508145437OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[082/000/A=000000OE8DKR
20250508145638OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[082/000/A=000000OE8DKR
20250509064806OE8DKR-7>APAT81,WIDE1-1,WIDE2-1,qAR,OE8XDR-10:!0000.00N/00000.00E[273/057/A=000000OE8DKR