APRS Packet Errors for DL4KSE-12 (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
20260111184134	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111184338	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111184657	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111184901	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111185521	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111185624	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAO,DB0NOT:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111185936	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111190140	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73
20260111190700	DL4KSE-12>APAT81-1,DB0MUC*,WIDE2-1,qAR,DB0TC-10:!3412.73N/10849.:0E(/A=000000Anytone 878 UV II Plus 73