APRS Packet Errors for ZL2BAU (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
20250614153751ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141537z0000.00NS00000.00W0
20250614160827ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141608z0000.00NS00000.00W0
20250614163414ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141634z0000.00NS00000.00W0
20250614170001ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141700z0000.00NS00000.00W0
20250614172656ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141726z0000.00NS00000.00W0
20250614175226ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141752z0000.00NS00000.00W0
20250614181813ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141818z0000.00NS00000.00W0
20250614184923ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141849z0000.00NS00000.00W0
20250614191146ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141911z0000.00NS00000.00W0
20250614194222ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *141942z0000.00NS00000.00W0
20250614201042ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142010z0000.00NS00000.00W0
20250614203413ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142034z0000.00NS00000.00W0
20250614205943ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142059z0000.00NS00000.00W0
20250614212206ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *142122z0000.00NS00000.00W0