APRS Packet Errors for EB3DMZ (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
20260731073518EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731080540EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731083602EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731090625EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731093648EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731100712EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731103735EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731110758EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731113822EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731120846EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731123910EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731130935EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731133957EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731141022EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731144047EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731151111EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731154136EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731161202EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731201522EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731204547EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731211609EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731214631EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731221653EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731224716EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731231740EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260731234802EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801001823EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801004845EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801011906EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801014927EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801021948EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801025010EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801032032EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801035054EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801042116EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801045137EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801052158EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801055219EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801062240EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
20260801065305EB3DMZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3DMZ-DP!12300.00N/45600.00rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz