APRS Packet Errors for 2E0YJR (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
202508070026312E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070058042E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070129532E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070201262E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070233002E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070304332E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070336052E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070407372E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
202508070439452E0YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)2E0YJR-DP!5147.84N/000-47.01rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz