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
20260209091215DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209094015DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209100815DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209103615DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209110415DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209113215DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209120015DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209122815DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209125615DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209132415DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209135215DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209142015DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM
20260209144815DO3MBJ-15>APLRG1,TCPIP*,qAC,T2PERTH:!L5xU6QE5c& GLoRa iGATE Pfaffenhofen JN58RM