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
20260318075519DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t043r000p...P...h100b10380 Lux:10345 WX-Berlstedt
20260318080320DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t043r000p...P...h100b10381 Lux:11082 WX-Berlstedt
20260318080904DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_135/00 g...t044r000p...P...h100b10381 Lux:11655 WX-Berlstedt
20260318081230DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t043r000p...P...h100b10380 Lux:11982 WX-Berlstedt
20260318100225DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_000/00 g...t048r000p...P...h100b10384 Lux:21680 WX-Berlstedt
20260318100442DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_000/00 g...t048r000p...P...h100b10384 Lux:21791 WX-Berlstedt
20260318100700DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t048r000p...P...h100b10383 Lux:21875 WX-Berlstedt