APRS Packet Errors for PD0SBH-12 (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
20260208151407PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208154407PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208161607PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208164407PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208171408PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208174408PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208181608PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208184408PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208191408PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208194409PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208201609PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard
20260208204409PD0SBH-12>APLOX1,TCPIP*,qAC,PD0SBH-LX:!L4QPhOprc& HLora iGate Valkenswaard