APRS Packet Errors for DK5VQ-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
20250816122639	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|$u%N\|
20250816124139	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|$v%N\|
20250816125639	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|$w%N\|
20250816131139	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|$x%N\|
20250816132639	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|$y%N\|
20250816134140	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|$z%N\|
20250816135640	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|${%N\|
20250816141140	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|%!%N\|
20250816142640	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|%"%N\|
20250816144140	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|%#%N\|
20250816145640	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|%$%N\|
20250816151140	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|%%%N\|
20250816152641	DK5VQ-10>APLRG1,TCPIP*,qAC,T2HUN:!LoRa APRS\|%&%N\|
20250816162641	DK5VQ-10>APLRG1,TCPIP,qAC,T2HUN:!LoRa APRS\|%%N\|