APRS Packet Errors for DB0KI-10 (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
20260208131821DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.75V
20260208134822DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.81V
20260208141822DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.87V
20260208144822DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.83V
20260208151822DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.87V
20260208154822DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.87V
20260208161822DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.81V
20260208164822DB0KI-10>APLRG1,TCPIP*,qAC,T2CAEAST:!L5{*qPW,Y& GLoRa APRS Ext=0.84V
20260208171822DB0KI-10>APLRG1,TCPIP*,qAC,T2BIO:!L5{*qPW,Y& GLoRa APRS Ext=0.79V
20260208174822DB0KI-10>APLRG1,TCPIP*,qAC,T2BIO:!L5{*qPW,Y& GLoRa APRS Ext=0.88V
20260208181822DB0KI-10>APLRG1,TCPIP*,qAC,T2BIO:!L5{*qPW,Y& GLoRa APRS Ext=0.75V
20260208184822DB0KI-10>APLRG1,TCPIP*,qAC,T2BIO:!L5{*qPW,Y& GLoRa APRS Ext=0.79V