APRS Packet Errors for SR3NJE (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
20251224122050SR3NJE>APNX02,SR3NJE*,qAR,SR3WR:!5220.71*r*Px3630 bAJemio|o .Pf
20251224125053SR3NJE>APNX02,SR3NJE*,qAR,SP3TLU:!5220.51S1516.41E#PHGs630 W3,SPn Jemiolow ot*5I
20251224125056SR3NJE>APNX02,SR3NJE*,qAR,SP3TLU:!5220.5qNS01516.41E#PHO3630 W3,SPn Je[ZoSPD
20251224142059SR3NJE>APNX02,SR3NJE*,qAR,SP3TLU:!7220.51NS01516.<1G/PHG363L,SPY{Zop. SP3DFR
20251224152110SR3NJE>APNX02,SR3NJE*,qAR,SQ1KSM-10:!5220.51NS01516.LQ$T630 W3,SPn Juoolow op. SP3DFr
20251224155135SR3NJE>APNX02,SR3NJE*,qAR,SQ1KSM-10:!5220.5&jr*PHG3630 _3SPn Jemioow op. Sp
20251224162108SR3NJE>APNX02,SR3NJE*,qAR,SQ1KSM-10:!5220.51NSNr*PHG3630 W3SPn Jemiolow ù0DFR
20251224162109SR3NJE>APNX02,SR3NJE*,qAR,SQ1KSM-10:!5220.51N*r*PHG3ӂ,*Jemi݁p>`sPsFR