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
20251207115556	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t050r000p...P...h100b10224 Lux:3979 WX-Berlstedt
20251207115814	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_270/00 g...t050r000p...P...h100b10224 Lux:3834 WX-Berlstedt
20251207115922	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t050r000p...P...h100b10223 Lux:4001 WX-Berlstedt
20251207120248	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t050r000p...P...h100b10222 Lux:4415 WX-Berlstedt
20251207121850	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t050r000p...P...h100b10222 Lux:2807 WX-Berlstedt
20251207121958	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t050r000p...P...h100b10222 Lux:2946 WX-Berlstedt
20251207124252	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_090/00 g...t050r000p...P...h100b10221 Lux:3618 WX-Berlstedt
20251207125527	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t050r000p...P...h100b10220 Lux:3064 WX-Berlstedt
20251207130111	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_225/00 g...t050r000p...P...h100b10221 Lux:3658 WX-Berlstedt
20251207134250	DL3APY-3>APRS,qAO,DL3APY-10:!5103.46N/01114.66E_180/00 g...t049r000p...P...h100b10220 Lux:2195 WX-Berlstedt