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
20260917075223DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t071r000p...P...h50b10296 Lux:15969 WX-Berlstedt
20260917083448DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t073r000p...P...h47b10295 Lux:12560 WX-Berlstedt
20260917084032DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_315/00 g...t071r000p...P...h51b10295 Lux:15075 WX-Berlstedt
20260917095505DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t074r000p...P...h43b10290 Lux:21093 WX-Berlstedt
20260917112323DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t075r000p...P...h40b10282 Lux:22620 WX-Berlstedt
20260917120441DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t074r000p...P...h41b10277 Lux:13709 WX-Berlstedt
20260917121134DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t074r000p...P...h40b10277 Lux:15704 WX-Berlstedt
20260917130054DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t077r000p...P...h35b10270 Lux:21112 WX-Berlstedt
20260917131222DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t073r000p...P...h38b10269 Lux:8648 WX-Berlstedt