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
20260820053440DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t078r000p...P...h55b10209 Lux:6981 WX-Berlstedt
20260820061013DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t078r000p...P...h55b10212 Lux:3643 WX-Berlstedt
20260820063744DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t078r000p...P...h54b10214 Lux:8037 WX-Berlstedt
20260820070148DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t084r000p...P...h45b10212 Lux:15977 WX-Berlstedt
20260820071316DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t088r000p...P...h41b10214 Lux:14328 WX-Berlstedt
20260820071425DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t083r000p...P...h46b10214 Lux:6450 WX-Berlstedt
20260820072336DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t086r000p...P...h44b10213 Lux:19939 WX-Berlstedt
20260820084611DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t085r000p...P...h40b10218 Lux:7042 WX-Berlstedt
20260820095242DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t088r000p...P...h33b10216 Lux:18940 WX-Berlstedt
20260820095826DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t090r000p...P...h31b10216 Lux:18490 WX-Berlstedt