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
20260723041053DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t062r000p...P...h66b10311 Lux:360 WX-Berlstedt
20260723042110DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t062r000p...P...h67b10311 Lux:593 WX-Berlstedt
20260723042544DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t062r000p...P...h68b10311 Lux:580 WX-Berlstedt
20260723042653DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t062r000p...P...h67b10311 Lux:573 WX-Berlstedt
20260723060737DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t063r000p...P...h64b10316 Lux:3144 WX-Berlstedt
20260723070130DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t060r000p...P...h71b10320 Lux:1722 WX-Berlstedt
20260723080910DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t063r000p...P...h70b10321 Lux:12261 WX-Berlstedt