APRS Packet Errors for DO6GZ-WX (last 24 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
20260522215613DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t058r000p...P...h100b10296 Lux:0 WX-Alfeld-OST
20260523073123DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_270/00 g...t082r000p...P...h65b10294 Lux:2628 WX-Alfeld-OST
20260523081313DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t082r000p...P...h67b10293 Lux:2494 WX-Alfeld-OST
20260523083408DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_225/00 g...t083r000p...P...h64b10291 Lux:2598 WX-Alfeld-OST
20260523084436DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t084r000p...P...h67b10291 Lux:2617 WX-Alfeld-OST
20260523094721DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_000/00 g...t086r000p...P...h61b10290 Lux:5535 WX-Alfeld-OST
20260523095749DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_135/00 g...t086r000p...P...h59b10287 Lux:8204 WX-Alfeld-OST
20260523124509DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_315/00 g...t083r000p...P...h47b10285 Lux:2525 WX-Alfeld-OST
20260523135822DO6GZ-WX>APRS,qAO,DO6GZ-L4:!5158.93N/00950.64E_090/00 g...t084r000p...P...h46b10284 Lux:3216 WX-Alfeld-OST