APRS Packet Errors for HJ4LSP-1 (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
20260208152039HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@152038h0618.33N/07526.70W-HK6RM_HKNET
20260208155040HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@155039h0618.33N/07526.70W-HK6RM_HKNET
20260208162041HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@162040h0618.33N/07526.70W-HK6RM_HKNET
20260208165041HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@165041h0618.33N/07526.70W-HK6RM_HKNET
20260208172042HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@172042h0618.33N/07526.70W-HK6RM_HKNET
20260208175043HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@175043h0618.33N/07526.70W-HK6RM_HKNET
20260208182044HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@182044h0618.33N/07526.70W-HK6RM_HKNET
20260208185045HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@185044h0618.33N/07526.70W-HK6RM_HKNET
20260208192046HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@192045h0618.33N/07526.70W-HK6RM_HKNET
20260208195047HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@195046h0618.33N/07526.70W-HK6RM_HKNET
20260208202047HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@202046h0618.33N/07526.70W-HK6RM_HKNET
20260208205048HJ4LSP-1>APWW11,TCPIP*,qAC,T2PERTH:@205047h0618.33N/07526.70W-HK6RM_HKNET