APRS Packet Errors for BV7SP-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
20260208145627BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208151006BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208152351BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208153741BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208155206BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208160546BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208161926BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208163231BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208164541BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208165916BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208171251BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208172531BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208173801BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208175201BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208180521BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208181926BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208183326BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208184706BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208185936BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208191244BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208192518BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208193941BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208195226BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208200521BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208201852BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz
20260208203256BV7SP-1>APRX29,TCPIP*,qAC,T2TAIPEI:!2233.69NV12022.22EaRPI(B3) + VP-DIGI + SMP-528(V) RX-only iGate 144.640Mhz