APRS Packet Errors for F5KJS-3 (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
20261120152647F5KJS-3>APRS,WIDE2-1,qAO,F4IKI-3:!0000.00N/00000.00E>198 67 37 0 35 a0 d0 h0
20261120153015F5KJS-3>APRS,WIDE2-1,qAR,ED1ZBA-3:!0000.00N/00000.00E>454 65 29 22 35 m321 M54 r3
20261120153342F5KJS-3>APRS,WIDE2-1,qAR,ED1ZBA-3:!0000.00N/00000.00E>626 64 31 23 35 m321 M56 r3
20261120153709F5KJS-3>APRS,WIDE2-1,qAR,ED2ZAD-3:!0000.00N/00000.00E>956 63 33 7 35 a3 d0 h0
20261120154037F5KJS-3>APRS,WIDE2-1,qAR,ED1ZBA-3:!0000.00N/00000.00E>297 60 34 20 36 a4 d0 h0
20261120154404F5KJS-3>APRS,WIDE2-1,qAR,ED2ZAD-3:!0000.00N/00000.00E>553 58 39 24 36 m321 M65 r3
20261120155648F5KJS-3>APRS,WIDE2-1,qAR,ED2ZAE-3:!0000.00N/00000.00E>708 52 64 0 37 m321 M77 r4
20261120160529F5KJS-3>APRS,F5ZEO-3*,qAR,F6DPH-10:!0000.00N/00000.00E>708 52 64 0 37 m321 M77 r4