APRS Packet Errors for KD5DK (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
20260208182714	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@182715h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208185715	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@185716h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208192715	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@192716h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208195716	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@195717h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208202716	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@202717h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208205717	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@205716h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208212717	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@212716h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208215717	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@215717h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208222718	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@222718h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208225719	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@225719h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208232719	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@232719h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1
20260208235720	KD5DK>APWW11,TCPIP*,qAC,T2ROMANIA:@235720h3237.01N9706.67WK448.775MHz T167 -500 WLNK-1