APRS Packet Errors for DL4JC-9 (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
20260208151711DL4JC-9>APOG77,WIDE1-1,WIDE2-2,qAR,DB0KOE-1:!/4mVRP5V`> !438.387MHz toff -760 En Route
20260208153128DL4JC-9>APOG77,WIDE1-1,WIDE2-2,qAR,DB0UT-10:!/4wk^P=AG> !438.300MHz toff -760 En Route
20260208154051DL4JC-9>APOG77,DB0LJ,WIDE1*,WIDE2-2,qAR,DB0UT-10:!/5&hUP>Ns> !438.300MHz toff -760 En Route
20260208155018DL4JC-9>APOG77,LX0APN-2,WIDE1*,WIDE2-2,qAR,ON1KDP-2:!/5)sWP9v^> !438.500MHz toff -760 En Route
20260208161545DL4JC-9>APOG77,WIDE1-1,WIDE2-2,qAR,DL1VED:!/59SeP5Y7> !439.537MHz toff -760 En Route
20260208162834DL4JC-9>APOG77,WIDE1-1,WIDE2-2,qAR,DB0IKS-15:!/5GK[P8C]> !439.275MHz toff -760 En Route
20260208163647DL4JC-9>APOG77,WIDE1-1,WIDE2-2,qAR,DB0IKS-15:!/5GO$P8S?> !439.275MHz toff -760 En Route
20260208164047DL4JC-9>APOG77,WIDE1-1,WIDE2-2,qAR,DB0IKS-15:!/5GO$P8S?> !439.275MHz toff -760 En Route