APRS Packet Errors for HS0BYW-C (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
20190116081114HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116081431HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116082128HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116084249HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116090249HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116091816HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116093815HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116095239HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz
20190116101108HS0BYW-C>APDG02,TCPIP*,qAC,HS0BYW-CS:!135919.80ND1003636.60E&RNG0001 2m Voice 145.55000MHz +0.0000MHz