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
20260722175319DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t073r000p...P...h43b10305 Lux:4540 WX-Berlstedt
20260722193038DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t069r000p...P...h50b10307 Lux:29 WX-Berlstedt
20260722204134DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t068r000p...P...h54b10306 Lux:0 WX-Berlstedt