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
20190324093056ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241403z4553.81S/17023.70E-QTH
20190324093116ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241403z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324100056ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241503z4553.81S/17023.70E-QTH
20190324100115ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241503z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324103055ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241503z4553.81S/17023.70E-QTH
20190324103115ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241503z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324110054ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241603z4553.81S/17023.70E-QTH
20190324110114ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241603z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324113053ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241603z4553.81S/17023.70E-QTH
20190324113113ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241603z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324120051ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241703z4553.81S/17023.70E-QTH
20190324120111ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241703z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324123051ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241703z4553.81S/17023.70E-QTH
20190324123111ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241703z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324130050ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241803z4553.81S/17023.70E-QTH
20190324130110ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241803z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324133048ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241803z4553.81S/17023.70E-QTH
20190324133108ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241803z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324140047ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241903z4553.81S/17023.70E-QTH
20190324140107ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241903z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324143046ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/241903z4553.81S/17023.70E-QTH
20190324143106ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*241903z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190324150045ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/242003z4553.81S/17023.70E-QTH
20190324150105ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*242003z4553.81SO17023.70E&146.650MHz : NODE OFFLINE