APRS Packet Errors for MB5WP (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
20250703170128	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703173154	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703180219	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703183245	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703190310	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703193335	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703200358	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703203422	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz
20250703210446	MB5WP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB5WP-DP!3800.00N/095-0.00WrRNG0034 IPSC2-DVSPh-A MMDVM 444.0000@+5.0 MHz