APRS Packet Errors for DJ1JAN-4 (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
20260209091948DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209095018DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209104212DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209111235DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/B=001/A=000115
20260209114306DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209121331DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209124353DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209134449DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209141516DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209144536DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115
20260209151602DJ1JAN-4>APRSMC,TCPIP*,qAR,DJ1JAN-3:!5345.50N0955.34ELqrv on Tg 26221#DJ1JAN-4/A=000115