APRS Packet Errors for DB0LOS (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
20180527001505DB0LOS>AP4R13,SR1NRW,SR3NWY,WIDE2*,qAR,SP3WBX:;DB0LOS *111111z5219.28N
20180527002509DB0LOS>AP4R13,SR3NWY*,WIDE2-1,qAR,SP3WBX:!5219.28Digi und 438,775 MHz FM-Relais
20180527012447DB0LOS>AP4R13,SR1NRW,SR3NPB,WIDE2*,qAR,SP3WBX:;DB0LOS *111111z52
20180527024117DB0LOS>AP4R13,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:!5219.28NS014
20180527030511DB0LOS>AP4R13,SR3NZG*,WIDE2-1,qAR,SP3WBX:!5219.28NE#PHG4570 W2,SPn Zerkow
20180527050505DB0LOS>AP4R13,SR3NZG,SR3NPB,WIDE2*,qAR,SP3WBX:!5402.26E#PHG3530 Wide-Digi und 438,775 MHz FM-Relais