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
20260312080622DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t050r000p...P...h100b10323 Lux:11246 WX-Berlstedt
20260312101109DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t054r000p...P...h100b10327 Lux:21586 WX-Berlstedt
20260312102602DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t055r000p...P...h100b10325 Lux:28845 WX-Berlstedt
20260312102711DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t056r000p...P...h100b10326 Lux:28944 WX-Berlstedt
20260312130253DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_135/00 g...t057r000p...P...h100b10312 Lux:20990 WX-Berlstedt
20260312130618DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t058r000p...P...h100b10311 Lux:19944 WX-Berlstedt
20260312134148DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t059r000p...P...h100b10307 Lux:17920 WX-Berlstedt