APRS Packet Errors for DL9TPA-2 (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
20260209104513	DL9TPA-2>APRS,WIDE1-1,WIDE2-1,qAR,DB0CSD:!5050.24N/01256.06E_.../...g...t040r000p000h91b10080 APRS-WX
20260209121513	DL9TPA-2>APRS,WIDE1-1,WIDE2-1,qAR,DB0CSD:!5050.24N/01256.06E_.../...g...t044r000p000h82b10073 APRS-WX
20260209140017	DL9TPA-2>APRS,WIDE1-1,WIDE2-1,qAR,DB0CSD:!5050.24N/01256.06E_.../...g...t043r000p000h81b10066 APRS-WX
20260209141512	DL9TPA-2>APRS,WIDE1-1,WIDE2-1,qAR,DB0CSD:!5050.24N/01256.06E_.../...g...t042r000p000h82b10066 APRS-WX
20260209151512	DL9TPA-2>APRS,WIDE1-1,WIDE2-1,qAR,DB0CSD:!5050.24N/01256.06E_.../...g...t041r000p000h83b10064 APRS-WX
20260209163014	DL9TPA-2>APRS,WIDE1-1,WIDE2-1,qAR,DB0CSD:!5050.24N/01256.06E_.../...g...t039r000p000h86b10062 APRS-WX