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
20190326192859ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270003z4553.81S/17023.70E-QTH
20190326192919ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270003z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326195858ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270103z4553.81S/17023.70E-QTH
20190326195918ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270103z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326202857ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270103z4553.81S/17023.70E-QTH
20190326202917ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270103z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326205855ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270203z4553.81S/17023.70E-QTH
20190326205915ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270203z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326212854ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270203z4553.81S/17023.70E-QTH
20190326212914ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270203z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326215853ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270303z4553.81S/17023.70E-QTH
20190326215913ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270303z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326222852ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270303z4553.81S/17023.70E-QTH
20190326222912ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270303z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326225851ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270403z4553.81S/17023.70E-QTH
20190326225911ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270403z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326232851ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270403z4553.81S/17023.70E-QTH
20190326232911ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270403z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190326235850ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270503z4553.81S/17023.70E-QTH
20190326235910ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270503z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190327002849ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270503z4553.81S/17023.70E-QTH
20190327002909ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270503z4553.81SO17023.70E&146.650MHz : NODE OFFLINE
20190327005847ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:/270603z4553.81S/17023.70E-QTH
20190327005907ZL4DM>APRS,DUD,WIDE3-2,qAR,ZL4DM-2:;IRLP-*270603z4553.81SO17023.70E&146.650MHz : NODE OFFLINE