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
20250324134633ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241346z0000.00NS00000.00W0
20250324141800ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241418z0000.00NS00000.00W0
20250324144512ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241445z0000.00NS00000.00W0
20250324150752ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241507z0000.00NS00000.00W0
20250324153049ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241530z0000.00NS00000.00W0
20250324160142ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241601z0000.00NS00000.00W0
20250324162928ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241629z0000.00NS00000.00W0
20250324165657ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241656z0000.00NS00000.00W0
20250324172210ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241722z0000.00NS00000.00W0
20250324175047ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241750z0000.00NS00000.00W0
20250324181651ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241816z0000.00NS00000.00W0
20250324183931ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241839z0000.00NS00000.00W0
20250324190427ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241904z0000.00NS00000.00W0
20250324193014ZL2BAU>APX220,TCPIP*,qAC,T2ZL:;Staging *241930z0000.00NS00000.00W0