APRS Packet Errors for OH3RBE-1 (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
20170526071415OH3RBE-1>APRX29,OH3RBE-5*,qAR,OH3HPV:;434.850-C*111111z6130.30N/02344.850MHz00 R40k City OH3
20170526071820OH3RBE-1>APRX29,OH3RBE-5*,qAR,OH3HPV:;ACUTA *111111z6130.33N/0234h +358 3 5657 0023 Emergd ACUTA
20170526075339OH3RBE-1>APRX29,OH3RBE-2*,qAR,OH3HPV:;ACUTA *111111z6130.33N/0234h +358 3 5657 00ency Ward ACUTA
20170526083609OH3RBE-1>APRX29,TRACE1-1,qAR,OH3HPV:;OH3NE *111178N/0234ub mtgs 50MHz T1
20170526100206OH3RBE-1>APRX29,OH3RBE-2*,qAR,OH3HPV:;434.800-A*111111z6122.11N/02254.800MHz00 R30k OH1RUG
20170526100601OH3RBE-1>APRX29,OH3RBE-2*,qAR,OH3HPV:;OH3NE 11z6129.3.90EyClMo/Th 1750MHz T1
20170526111203OH3RBE-1>APRX29,qAR,OH3HPV:;NAUKI111z612946.64E/Wt there!
20170526111921OH3RBE-1>APRX29,OH3RBE-3*,qAR,OH3HPV:;145.750-C*11114.60Er14 T123 -0Tampere E