APRS Packet Errors for ZL4DM (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
20180920050215ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/200709z4553.81S/17023.70E-QTH
20180920050235ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*200709z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920053214ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/200809z4553.81S/17023.70E-QTH
20180920053234ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*200809z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920060213ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/200809z4553.81S/17023.70E-QTH
20180920060233ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*200809z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920063212ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/200909z4553.81S/17023.70E-QTH
20180920063232ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*200909z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920070210ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/200909z4553.81S/17023.70E-QTH
20180920070230ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*200909z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920073209ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/201009z4553.81S/17023.70E-QTH
20180920073229ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*201009z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920080208ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/201009z4553.81S/17023.70E-QTH
20180920080228ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*201009z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920083208ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/201109z4553.81S/17023.70E-QTH
20180920083228ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*201109z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920090207ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/201109z4553.81S/17023.70E-QTH
20180920090227ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*201109z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920093206ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/201209z4553.81S/17023.70E-QTH
20180920093226ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*201209z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920100205ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/201209z4553.81S/17023.70E-QTH
20180920100225ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*201209z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20180920103203ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/201309z4553.81S/17023.70E-QTH
20180920103223ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*201309z4553.81SO17023.70E&146.650MHz : NODE OFFLINE