APRS Packet Errors for CT2HBM (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
20260208144629CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208151629CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208154629CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208161629CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208164629CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208171629CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208174630CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208181630CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208184630CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208191630CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208194630CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS
20260208201630CT2HBM>APLRG1,TCPIP*,qAC,T2BC:!L:ksyL3ui# GLoRa APRS