APRS Packet Errors for MB7UNM (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
20260208125239MB7UNM>APBPQ1,qAR,M0SDM-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208132239MB7UNM>APBPQ1,qAR,M0SDM-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208135239MB7UNM>APBPQ1,qAR,M0SDM-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208142239MB7UNM>APBPQ1,qAR,2E0FKC-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208145240MB7UNM>APBPQ1,qAR,2E0FKC-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208152239MB7UNM>APBPQ1,qAR,G7NRU-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208155239MB7UNM>APBPQ1,qAR,2E0FKC-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208162239MB7UNM>APBPQ1,qAR,G7NRU-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208165239MB7UNM>APBPQ1,qAR,G7NRU-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208172241MB7UNM>APBPQ1,qAR,2E0FKC-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208175242MB7UNM>APBPQ1,qAR,M0SDM-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX
20260208182239MB7UNM>APBPQ1,qAR,G7NRU-10:!5259.04N/00107.02W-MB7UNM Nottingham IO92KX