APRS Packet Errors for SV4RWY-7 (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
20260208181323SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208182326SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208183339SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208185346SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208190350SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208191354SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208192358SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208193402SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208194406SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208195410SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208200414SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208201418SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208205428SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208210436SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208211440SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208212444SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208213449SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208214453SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208215457SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208220500SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208221504SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208222507SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208223510SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208224514SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208225518SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208230526SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208231529SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208232534SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208233537SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208234541SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260208235545SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R
20260209000550SV4RWY-7>APDMRP,SV4R,TCPIP*,qAU,T2KOBLENZ:!3922.23N/02154.55E[ John via DMR+ SV4R