APRS Packet Errors for KH KPE (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
20260209110006	OE3MQK>APN100,TCPIP,qAC,T2SYDNEY:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209113005	OE3MQK>APN100,TCPIP,qAC,T2PERTH:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209120005	OE3MQK>APN100,TCPIP,qAC,T2BC:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209123005	OE3MQK>APN100,TCPIP,qAC,T2SYDNEY:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209130006	OE3MQK>APN100,TCPIP,qAC,T2PANAMA:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209133004	OE3MQK>APN100,TCPIP,qAC,T2ROMANIA:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209140006	OE3MQK>APN100,TCPIP,qAC,T2SPAIN:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209143004	OE3MQK>APN100,TCPIP,qAC,T2EISBERG:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209150006	OE3MQK>APN100,TCPIP,qAC,T2DENMARK:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209153003	OE3MQK>APN100,TCPIP,qAC,T2ERFURT:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209160004	OE3MQK>APN100,TCPIP,qAC,T2CAEAST:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing
20260209163004	OE3MQK>APN100,TCPIP,qAC,T2CHILE:;KH KPE 111111z4812.59N/01616.88EhKlinik Penzing