APRS Packet Errors for DK3RW-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
20260209090401DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209092413DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209094424DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209102340DK3RW-2>APNU19,DB0REI-10*,WIDE2-2,qAR,DB0WIZ-15:!5040.01N/00859.56E/Test
20260209104349DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209110401DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209112413DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209114424DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209122339DK3RW-2>APNU19,DB0REI-10*,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209124349DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209130401DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209132412DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209134423DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209142338DK3RW-2>APNU19,WIDE1-1,WIDE2-2,qAO,DB0KH-10:!5040.01N/00859.56E/Test
20260209144350DK3RW-2>APNU19,DB0REI-10*,WIDE2-2,qAR,DB0KT-2:!5040.01N/00859.56E/Test