APRS Packet Errors for SP9MUF-14 (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
20260420055328SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200553z/549"SP?5_r6Gg004t044r000p...P008h75b10197L034
20260420063904SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200638z/549"SP?5_m3Gg003t046r000p...P008h74b10197L052
20260420073953SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200739z/549"SP?5_v6Gg004t046r000p...P008h73b10197L045
20260420074457SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200744z/549"SP?5_"6Gg005t046r000p...P008h73b10197L040
20260420085048SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200850z/549"SP?5_p1Gg003t046r000p...P008h70b10143L102
20260420092112SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200921z/549"SP?5_m7Gg006t046r000p...P008h68b10142L136
20260420093120SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200931z/549"SP?5_x7Gg005t046r000p...P008h69b10142L114
20260420093624SP9MUF-14>APLRG1,WIDE1-1,qAO,SP9KKK-1:@200936z/549"SP?5_p9Gg006t046r000p...P008h69b10141L136