APRS Packet Errors for YM3KYM-1 (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
20261023233614YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:!3907.47N/|2709.15E#TRAC Bergama Sb 439.16250 TRX ;8,5T
20261024022923YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:!3907.45N/02709:15E#TRAC Bergama Sb 439.18
20261024031011YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:!3907.45N/02709.)-=#TREG Bergama Sa 439.16250 WRX 88,5T
20261024032044YM3KYM-1>APBK20,WIDE1-1,WIDE2-1,qAR,YM3KC-8:!39˜“‰ªr½02709.15E#TRAC Bergama Sb 439.18750 TRX 88,5T
20261024040603YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:!307.45N/027°9.1-]# TRAC Aergama Sb. Digirepeater
20261024042125YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:!1907.,5N/027 9.15E#TRA# Bergama Sb 439.16250 TRX 88,5T
20261024052803YM3KYM-1>APBK20,TA3F-14,TA3ACE-10*,qAS,TB3ACE-14:!3907n´4N/02709.15E#DRA[ Bergama Sb 439.18750 TRX 88,5T
20261024084025YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:!3907.4=N/02709.±5E#&TRAC Bergama Sb. Digirepeater
20261024124333YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:!3907,45N/02709.35E# TRAC Bergama Sb- DigirepeQter
20261024144630YM3KYM-1>APBK20,TA3F-14,TB3ACE-10*,qAS,TB3ACE-14:)3907.45N/02709.15E# TSAC Bergama Sb. DigirepeQter