APRS Packet Errors for EA4ALM (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
20181216095154EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11WrRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181216100736EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181216102307EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181216103829EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181216105351EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181216110915EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181216112454EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181216114017EA4ALM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4ALM-DP!4037.50N/-03-58.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz