APRS Packet Errors for BH4GZK-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
20260209105536BH4GZK-1>APN000,WIDE1-1,WIDE2-1,qAS,BH4DBZ-10:=3107.75N/12123.07E-bh4gzk base 13.81V
20260209105910BH4GZK-1>APN000,TCPIP*,qAC,T2TAIPEI:=3107.75N/12123.07E-bh4gzk base 13.8V
20260209112536BH4GZK-1>APN000,WIDE1-1,WIDE2-1,qAS,BH4FEN-10:=3107.75N/12123.07E-bh4gzk base 13.80V
20260209112910BH4GZK-1>APN000,TCPIP*,qAC,T2TAIPEI:=3107.75N/12123.07E-bh4gzk base 13.8V
20260209115536BH4GZK-1>APN000,WIDE1-1,WIDE2-1,qAS,BH4FEN-10:=3107.75N/12123.07E-bh4gzk base 13.77V
20260209115856BH4GZK-1>APN000,WIDE1-1,WIDE2-1,qAO,BH4CRV-15:=3107.75N/12123.07E-bh4gzk base 13.77V
20260209115911BH4GZK-1>APN000,TCPIP*,qAC,T2TAIPEI:=3107.75N/12123.07E-bh4gzk base 13.8V
20260209122536BH4GZK-1>APN000,WIDE1-1,WIDE2-1,qAS,BH4FEN-10:=3107.75N/12123.07E-bh4gzk base 13.80V
20260209122910BH4GZK-1>APN000,TCPIP*,qAC,T2TAIPEI:=3107.75N/12123.07E-bh4gzk base 13.8V
20260209125536BH4GZK-1>APN000,WIDE1-1,WIDE2-1,qAS,BH4DBZ-10:=3107.75N/12123.07E-bh4gzk base 13.79V
20260209125911BH4GZK-1>APN000,TCPIP*,qAC,T2TAIPEI:=3107.75N/12123.07E-bh4gzk base 13.8V
20260209132536BH4GZK-1>APN000,WIDE1-1,WIDE2-1,qAS,BH4FEN-10:=3107.75N/12123.07E-bh4gzk base 13.78V
20260209132911BH4GZK-1>APN000,TCPIP*,qAC,T2TAIPEI:=3107.75N/12123.07E-bh4gzk base 13.8V