APRS Packet Errors for E20TWR-2 (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
20260208214800E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082147z1359.38N/10037.09E_000/000g000t085r...p...P...h67b10130L000 < Stanby 145.1500 MHz.> T=29° H=67% P=1013
20260208214811E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082148z1359.38N/10037.09E_< Stanby 145.1500 MHz.> T=29° H=67% P=1013
20260208215824E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082158z1359.38N/10037.09E_000/000g000t085r...p...P...h67b10130L000 < Stanby 145.1500 MHz.> T=29° H=67% P=1013
20260208215835E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082158z1359.38N/10037.09E_< Stanby 145.1500 MHz.> T=29° H=67% P=1013
20260208220848E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082208z1359.38N/10037.09E_000/000g000t085r...p...P...h66b10130L000 < Stanby 145.1500 MHz.> T=29° H=66% P=1013
20260208220859E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082208z1359.38N/10037.09E_< Stanby 145.1500 MHz.> T=29° H=66% P=1013
20260208221912E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082219z1359.38N/10037.09E_000/000g000t085r...p...P...h66b10130L000 < Stanby 145.1500 MHz.> T=29° H=66% P=1013
20260208221923E20TWR-2>AESPG4,TCPIP*,qAC,T2HAKATA:@082219z1359.38N/10037.09E_< Stanby 145.1500 MHz.> T=29° H=66% P=1013