APRS Packet Errors for DB0MM (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
20190615214946DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190615220948DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190615222948DB0MM>APRS,TCPIP*,qAC,T2CAEAST:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190615224950DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190615230951DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190615232952DB0MM>APRS,TCPIP*,qAC,T2CAEAST:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190615234954DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190616000955DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190616002955DB0MM>APRS,TCPIP*,qAC,T2CAEAST:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190616004957DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM
20190616010958DB0MM>APRS,qAR,DE1TBK-10:;438.850- *11111z4725.25N/01059.08Er1750 R99k DB0ZU UHF FM