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
20261002203427SP9MUF-14>APLRG1,WIDE1-1,qAR,SP9KPS-1:@022034z/549"SP?5_+!Gg000t050r000p...P000h91b10327L000
20261002204933SP9MUF-14>APLRG1,SP9KPS-1,WIDE1*,qAO,SR9EMP-1:@022049z/549"SP?5_+!Gg000t050r000p...P000h91b10327L000
20261002205435SP9MUF-14>APLRG1,WIDE1-1,qAR,SP9KPS-1:@022054z/549"SP?5_+!Gg000t050r000p...P000h91b10327L000
20261002210439SP9MUF-14>APLRG1,SP9KPS-1,WIDE1*,qAR,SP9POL-2:@022104z/549"SP?5_+!Gg000t050r000p...P000h92b10327L000
20261002214957SP9MUF-14>APLRG1,WIDE1-1,qAR,SP9KPS-1:@022149z/549"SP?5_+!Gg000t048r000p...P000h93b10330L000
20261002222515SP9MUF-14>APLRG1,WIDE1-1,qAR,SP9KPS-1:@022225z/549"SP?5_+!Gg000t046r000p...P000h94b10332L000
20261002223520SP9MUF-14>APLRG1,WIDE1-1,qAR,SP9KPS-1:@022235z/549"SP?5_+!Gg000t046r000p...P000h94b10333L000