APRS Packet Errors for DO6GZ-WX (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
20251214091630DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_315/00 g...t042r000p...P...h100b10280 Lux:595 WX-Alfeld-OST
20251214105038DO6GZ-WX>APRS,qAO,DO6GZ-L3:!5158.93N/00950.64E_315/00 g...t044r000p...P...h100b10272 Lux:896 WX-Alfeld-OST
20251214115323DO6GZ-WX>APRS,qAO,DO6GZ-L3:!5158.93N/00950.64E_270/00 g...t044r000p...P...h100b10268 Lux:804 WX-Alfeld-OST
20251214121418DO6GZ-WX>APRS,qAO,DO6GZ-L3:!5158.93N/00950.64E_270/00 g...t044r000p...P...h100b10266 Lux:640 WX-Alfeld-OST
20251214133758DO6GZ-WX>APRS,qAO,DO6GZ-L3:!5158.93N/00950.64E_000/00 g...t043r000p...P...h100b10258 Lux:523 WX-Alfeld-OST
20251214141948DO6GZ-WX>APRS,qAO,DO6GZ-L3:!5158.93N/00950.64E_180/00 g...t042r000p...P...h100b10255 Lux:256 WX-Alfeld-OST
20251214145111DO6GZ-WX>APRS,qAO,DL8KM-10:!5158.93N/00950.64E_270/00 g...t042r000p...P...h100b10255 Lux:81 WX-Alfeld-OST