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
20260204200035	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t027r000p...P...h100b10105 Lux:0 WX-Berlstedt
20260204213303	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t027r000p...P...h100b10099 Lux:0 WX-Berlstedt
20260204221842	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t027r000p...P...h100b10098 Lux:0 WX-Berlstedt
20260204222059	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t027r000p...P...h100b10098 Lux:0 WX-Berlstedt
20260204223116	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t026r000p...P...h100b10096 Lux:0 WX-Berlstedt
20260204223224	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_000/00 g...t026r000p...P...h100b10096 Lux:0 WX-Berlstedt
20260204223333	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t026r000p...P...h100b10095 Lux:0 WX-Berlstedt
20260205013721	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t025r000p...P...h100b10087 Lux:0 WX-Berlstedt