APRS Packet Errors for LA7F-10 (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
20260208055240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@055238h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208062240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@062238h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208065240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@065238h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208072240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@072238h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208075240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@075238h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208082240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@082238h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208085240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@085238h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208092240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@092237h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208095240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@095237h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208102240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@102237h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208105240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@105237h6715.85NI01522.98E&PHG4460APRS-IGate Fauske
20260208112240LA7F-10>APWW10,TCPIP*,qAC,T2ERFURT:@112237h6715.85NI01522.98E&PHG4460APRS-IGate Fauske