APRS Packet Errors for SP1TRX-8 (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
20241223203127SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38U/R.:\_ .Q.../...g...t077h..b10083Tomek QRV 145.550 MHz |(@%V|
20241223205129SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38U!R.:W_ SQ.../...g...t078h..b10088Tomek QRV 145.550 MHz |(A%V|
20241223211131SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38TmR.:P_ *Q.../...g...t079h..b10084Tomek QRV 145.550 MHz |(B%V|
20241223212132SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38TcR.:M_ $Q.../...g...t079h..b10102
20241223214134SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38UMR.:__ `Q.../...g...t080h..b10089
20241223220136SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38T-R.:c_ /Q.../...g...t080h..b10128
20241223221137SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38TsR.:U_ LQ.../...g...t080h..b10102Tomek QRV 145.550 MHz |(E%V|
20241223222138SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38U-R.:h_ !Q.../...g...t080h..b10085
20241223232144SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38TrR.:Z_ jQ.../...g...t081h..b10111
20241224015159SP1TRX-8>APLRT1,WIDE1-1,qAR,SP1TRX-10:!/38U!R.:__ $Q.../...g...t067h..b10146Tomek QRV 145.550 MHz |(P%V|