APRS Packet Errors for 2E0YNT (last 24 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
201806241630072E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@241630z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806241700112E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@241700z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806241730122E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@241730z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806241800152E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@241800z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806241830142E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@241830z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806241900142E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@241900z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806241930192E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@241930z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242000182E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242000z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242030172E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242030z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242100222E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242100z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242130182E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242130z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242200192E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242200z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242230172E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242230z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242300182E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242300z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806242330172E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@242330z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250000182E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250000z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250030192E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250030z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250100192E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250100z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250130202E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250130z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250200302E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250200z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250230092E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250230z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250300172E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250300z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250330202E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250330z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1
201806250400232E0YNT>APRS,TCPIP*,qAS,PI1DMR-14:@250400z5232.100N/00014.40WQMMDVM DVMega 430.6375/430.6375 CC1