APRS Packet Errors for 2M0SBP-5 (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
202609272205532M0SBP-5>APZDMR,TCPI,T2D,qAR,AE7AF:=64N550.41W$H 60 etrible
202609272240112M0SBP-5>MR,TCPHILE,qAR,AE7AF:=550.45r P60 pedestr
202609280011352M0SBP-5>APZCPIq,qAR,AE7AF:=550.4ra obie
202609280121032M0SBP-5>APZDMR,CP,T2TAS,qAR,AE7AF:=5654.65N/00550.$ytera P60 petrian
202609280137012M0SBP-5>APZDMR,TCPIP*,qAC,T2LAUSITZ:=56N/0055ra P60 pedeian mobil
202609280216522M0SBP-5>PDENMARK,qAR,AE7AF:=5654N/00550W$Hyera P60 estrian mobile
202609280249512M0SBP-5>APMR,TCPIP*,qAS,AE7AF:=5654./00550.$Hyter60 pedrian m