APRS Packet Errors for DL3APY-3 (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
20241223210112	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t034r000p...P...h100b10268 Lux:0 WX-Berlstedt
20241223213745	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t034r000p...P...h100b10272 Lux:0 WX-Berlstedt
20241223214652	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t034r000p...P...h100b10274 Lux:0 WX-Berlstedt
20241223215018	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t034r000p...P...h100b10274 Lux:0 WX-Berlstedt
20241223215126	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t034r000p...P...h100b10274 Lux:0 WX-Berlstedt
20241223220143	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t034r000p...P...h100b10275 Lux:0 WX-Berlstedt
20241223221959	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t034r000p...P...h100b10277 Lux:0 WX-Berlstedt
20241223223125	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t034r000p...P...h100b10278 Lux:0 WX-Berlstedt
20241223231921	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t033r000p...P...h100b10283 Lux:0 WX-Berlstedt