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
20260201102343	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t027r000p...P...h100b10227 Lux:7890 WX-Berlstedt
20260201102600	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t027r000p...P...h100b10227 Lux:7804 WX-Berlstedt
20260201102817	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t027r000p...P...h100b10228 Lux:7737 WX-Berlstedt
20260201102926	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t027r000p...P...h100b10227 Lux:7718 WX-Berlstedt
20260201103035	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t027r000p...P...h100b10227 Lux:7711 WX-Berlstedt
20260201112423	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t028r000p...P...h100b10223 Lux:7124 WX-Berlstedt
20260201112857	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t028r000p...P...h100b10223 Lux:6890 WX-Berlstedt
20260201113332	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_045/00 g...t028r000p...P...h100b10222 Lux:7316 WX-Berlstedt