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
20260219211330	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_135/00 g...t024r000p...P...h100b10260 Lux:0 WX-Berlstedt
20260219212237	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_000/00 g...t024r000p...P...h100b10261 Lux:0 WX-Berlstedt
20260219213254	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t024r000p...P...h100b10263 Lux:0 WX-Berlstedt
20260219213511	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t024r000p...P...h100b10263 Lux:0 WX-Berlstedt
20260219214527	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t024r000p...P...h100b10266 Lux:0 WX-Berlstedt
20260219220925	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t024r000p...P...h100b10269 Lux:0 WX-Berlstedt
20260219221359	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t024r000p...P...h100b10270 Lux:0 WX-Berlstedt
20260219221507	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_000/00 g...t024r000p...P...h100b10270 Lux:0 WX-Berlstedt
20260219221616	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t024r000p...P...h100b10269 Lux:0 WX-Berlstedt