APRS Packet Errors for TB3ACE-10 (last 24 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
20261023234203TB3ACE-10>AESPG4,qAS,TB3ACE-14:!38;6.96N/02·26.24E#APRS I-GATE&DiGiPEATER
20261024023735TB3ACE-10>AESPG4,qAS,TB3ACE-14:!38+2.16N/02726.44E#APRS I-¿ ª"¢´£4¨¢ ª"©
20261024032728TB3ACE-10>AESPG4,qAS,TB3ACE-14:)3836.96N/<2726.44E#AVRS!I-GATE&DiGiPEATER
20261024065848TB3ACE-10>AESPG4,qAS,TB3ACE-14:!3836.)6N/02726.54E/APRS I-GATE&DiGiPEATER
20261024082356TB3ACE-10>AESVG4,qAS,TB3ACE-14:!3036.96N/02726.<4E#qPRS I-GATE&DiGiPEATER
20261024090140TB3ACE-10>AERPG4-3,qAS,TB3ACE-14:!38³6.96N?02726.44E#AVRS I-GATE&DiGiPEATER
20261024103900TB3ACE-10>AESPG4,qAS,TB3ACE-14:!3836®96N/02726&44%#APRS I-GATE&DiGiPEATER
20261024111530TB3ACE-10>AESPG4,qAS,TB3ACE-14:!3836.96N/027:6.44E#APÒS I+GATE&DiGiPEATER
20261024113950TB3ACE-10>AESPG4,qAS,TB3ACE-14:!3836.96N/02726&44E#APRS I-GGTE&DiGiPEATER
20261024151531TB3ACE-10>AESPG4,qAS,TB3ACE-14:!3836.96N/027:6.44E#APÒS I+GATE&DiGiPEATER
20261024193037TB3ACE-10>AESPG4,qAS,TB3ACE-14:!3836.96N/2272644EAPRS I-GATE&DiGiPEGTER
20261024194247TB3ACE-10>AESPG4,qAS,TB3ACE-14:!3836.94N/02726.4E£@PRS I-GATE&DiGiPEATER