APRS Packet Errors for DG8OAA-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
20260209144043DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209151044DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209154045DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209161046DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209164047DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209171048DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209174049DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209181050DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209184051DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209191052DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209194053DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause
20260209201054DG8OAA-2>APX210,TCPIP*,qAC,T2KA:=5217.95N/00928.79EyJoerg zu Hause