APRS Packet Errors for F5KJI-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
20260923125809F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>553 80 9 323 37 m320 M75 r5
20260923130131F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>788 77 9 325 37 a1 d0 h1
20260923130453F5KJI-7>APRS,WIDE2-1,qAR,F6EOB-3:!0000.00N/00000.00E>7 74 10 322 38 a2 d0 h1
20260923130815F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>267 74 7 325 38 m320 M82 r5
20260923131136F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>536 73 6 324 38 a4 d0 h1
20260923131458F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>830 72 7 322 38 m320 M88 r5
20260923131819F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>137 69 9 324 39 m320 M91 r5
20260923132139F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>453 68 7 322 39 a7 d0 h1
20260923132500F5KJI-7>APRS,WIDE2-1,qAR,F6ZAF:!0000.00N/00000.00E>743 63 9 322 39 a8 d0 h1
20260923132758F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>973 60 19 321 39 a0 d0 h1
20260923133117F5KJI-7>APRS,WIDE2-1,qAR,F6ZAF:!0000.00N/00000.00E>270 59 12 321 40 a1 d0 h1
20260923134347F5KJI-7>APRS,WIDE2-1,qAO,EB2BRA-10:!0000.00N/00000.00E>162 55 13 321 41 m320 M111 r6