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
20260806062439	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t080r000p...P...h44b10314 Lux:-2 WX-Berlstedt
20260806072152	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t085r000p...P...h36b10313 Lux:-2 WX-Berlstedt
20260806072409	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t084r000p...P...h37b10314 Lux:-2 WX-Berlstedt
20260806074119	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t082r000p...P...h37b10315 Lux:-2 WX-Berlstedt
20260806080738	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t086r000p...P...h34b10314 Lux:-2 WX-Berlstedt
20260806082705	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t086r000p...P...h36b10314 Lux:-2 WX-Berlstedt
20260806085649	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t087r000p...P...h37b10312 Lux:-2 WX-Berlstedt
20260806095511	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t085r000p...P...h35b10313 Lux:-2 WX-Berlstedt