APRS Packet Errors for DL4NBA-1 (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
20260208132344	DL4NBA-1>APTW01,WIDE2-2,qAR,DB0VOX:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208134840	DL4NBA-1>APTW01,WIDE2-2,qAR,DB0VOX:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208141336	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208143832	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208150330	DL4NBA-1>APTW01,WIDE2-2,qAR,DB0VOX:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208152827	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208155322	DL4NBA-1>APTW01,WIDE2-2,qAR,DB0VOX:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208161819	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208164315	DL4NBA-1>APTW01,WIDE2-2,qAR,DB0VOX:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208170812	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208173307	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208175803	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208182259	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth
20260208184755	DL4NBA-1>APTW01,WIDE2-2,qAR,DK1EC-1:!4926.21N/01049.64E_/WX-MBC Fuerth