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
20190218005915ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180502z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218015913ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180602z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218022912ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180702z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218025911ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180702z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218032910ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180802z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218035909ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180802z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218042909ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180902z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218045907ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*180902z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218052906ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*181002z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218055905ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*181002z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190218062904ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*181102z4553.81SO17023.70E&146.650MHz : NODE OFFLINE