APRS Packet Errors for DH7LK-5 (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
20260208151328	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_045/004g006t035r p P000h96b KU2k
20260208154328	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_098/002g004t035r p P000h97b KU2k
20260208161329	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_055/001g004t034r p P000h97b KU2k
20260208164340	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_000/000g000t034r p P000h98b KU2k
20260208171341	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_000/000g000t034r p P000h98b KU2k
20260208174342	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_000/000g000t034r p P000h99b KU2k
20260208181342	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_096/000g004t034r p P000h99b KU2k
20260208184343	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_118/000g002t034r p P000h99b KU2k
20260208191344	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_111/001g004t033r p P000h99b KU2k
20260208194345	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_096/004g008t033r p P000h98b KU2k
20260208201345	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_110/003g005t034r p P000h98b KU2k
20260208204346	DH7LK-5>APK102,DB0AVH,qAR,DM0RBB:=5225.38N/01309.68E_101/002g004t034r p P000h98b KU2k