APRS Packet Errors for DO3MBJ-15 (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
20260208130812DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208133612DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208140412DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208143212DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208150012DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208152812DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208155612DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208162412DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208165212DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208172013DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208174813DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208181613DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260208184413DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM