APRS Packet Errors for HS1AL-1 (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
20250913071401HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@L&13z1447.910040.IlopbuZT=37° H=48% P=1006
20250913081550HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@130815z1447.03N/10r3ErAR lopburi T=37° H=45%1005
20250913083108HS1AL-1>AESPG4,qAR,E27ASY-2:@130831z1447.03N)r*}00/000g000t100r...p...P...h45b10050L000 AR lopburi T=37° H=45% P=1005
20250913084647HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@130846z1ӓ r10040*Ilopburi T=37° H=44% P=1005
20250913091734HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@L&17z1447.r10040.63E_000/000g000t09N. ..P...h0040L00Ilopburi T=37° H=46% P=1004
20250913094830HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@L&ʢ447.&)r*}00/000g000t098r...p...P...h49b10040LIlopburi T=36° H=49% P=1004
20250913112126HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@131121z1447.03N/100rE_000/0:00t097r ..P...h50b10050L000 AR lopburi T=36° H=50% 1005
20250913120806HS1AL-1>AEi94,TCPIP*,qAC,T2HAKATA:@131208z1447.03N/10040.*IlopbuZT=34° H=55% P=1006