APRS Packet Errors for CEDRMT (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
20251013150510CEDRMT>BEACON,qAR,ABAJO:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013151510CEDRMT>BEACON,qAR,ABAJO:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013152510CEDRMT>BEACON,qAR,ABAJO:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013153510CEDRMT>BEACON,qAR,ABAJO:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013154510CEDRMT>BEACON,qAR,HORNMT:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013154920CEDRMT>APN383,qAR,HORNMT:!3910.29NS11036.59#W#PHG3838/W2,UTn kbKB7K
20251013155510CEDRMT>BEACON,qAR,ABAJO:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013160510CEDRMT>BEACON,qAR,ABAJO:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013170510CEDRMT>BEACON,qAR,HORNMT:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL
20251013171510CEDRMT>BEACON,qAR,ABAJO:;147.140XY111111z3910.29N/11036.59WrT885 r50m WB7REL