APRS Packet Errors for OK2MOP-9 (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
20250711140959OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IU`S-nL_ (Q.../...g...t084r...p...P...h47b10186
20250711145015OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IUkS-n;_ )Q.../...g...t090r...p...P...h38b10191
20250711150019OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IUWS-nL_ -Q.../...g...t091r...p...P...h37b10195
20250711153032OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IU[S-n1_ wQ.../...g...t091r...p...P...h35b10173
20250711154036OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IU`S-n9_ =Q.../...g...t090r...p...P...h35b10209
20250711155040OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IV*S-nb_ %Q.../...g...t090r...p...P...h35b10181
20250711160044OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IUTS-nY_ tQ.../...g...t089r...p...P...h34b10173
20250711162052OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5IUYS-nE_ #Q.../...g...t086r...p...P...h35b10183
20250711164946OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5ITZS-nk_ rQ.../...g...t082r...p...P...h38b10167Car - Meg.III Bat=4.17V (184mA)
20250711165951OK2MOP-9>APLRT1,WIDE1-1,qAO,OK0BDL-10:!/5ITdS-nJ_ *Q.../...g...t081r...p...P...h39b10188