APRS Packet Errors for SKZ (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
20260208145003	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208152004	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208155003	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208162004	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208165004	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208172003	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208175004	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208182003	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208185004	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208192003	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz
20260208195004	SKZ>APRS,qAc,DB0DBT:!5124.90N/01216.28E/SKZ NDB 357kHz