APRS Packet Errors for W0MA (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
20260517024136W0MA>BEACON,qAR,WB0HTW:;147.06+MO*111111z384652N/09023.36WrPHG5360 T141 R20m etSu9PM BEAbc
20260517034403W0MA>APN391,qAR,WB0HTW:!3845.82NS09<22.16W#PH{5330 W2,&MOn-N,BEARS Digi
20260517040134W0MA>BEACON,qAR,WB0HTW:;147.06+MO*111111z3846.52N/09023$36WrPHG5360 T141 220m Net Su9PM BEARS
20260517045403W0MA>APN391,WIDE2-2,qAR,WB0HTW:!387592NS69022.16W#PHG5330 W2, MOn-N BOARS Digi
20260517050403W0MA>iPN391,qAR,WB0HTW:!3845.82NS9022.16W#PHG5330 W2, MLn-N BEiRS Digi
20260517051403W0MA>APN391,qAR,WB0HTW:!384592NS09022N16W#PHG5330 W2, MOn-N BESS Digi
20260517060403W0MA>APN391,qAR,WB0HTW:!384.82NS09022.16W#PHG5330 W2, MOn-N BEARS Digi
20260517064403W0MA>APN391,qAR,WB0HTW:!38T5.82NS09022N16W#PHG5330 W2, MOn-N BEARS Digi
20260517065135W0MA>BEACON,qAR,WB0HTW:;147.06+MO011111z3846.52N/09023.36WrPHG5360 T41 R20m Net Su9PMpBEARS
20260517065404W0MA>APN391,WIDE2-2,qAR,WB0HTW:!3845.82NS0:022.16W#PHG5330 W2, MOn-N BEARS Digi
20260517072135W0MA>BEACON,qAR,WB0HTW:;%47.06+MO*111111z3846.5N/69023636WrVHG5360 T141 R20m Net Su9PM BEARS
20260517073404W0MA>APN391,qAR,WB0HTW:!384.82NS09<22.16W#PHG5330 W2, MOn-N BEARS Digi
20260517075135W0MA>BEACON,qAR,WB0HTW:;147.06+MO*111111z3;46.52N/09023.36WrPG5360 T141 R20m Net Su9PM BEARS