APRS Packet Errors for OE3PYC-7 (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
20251215103238	OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,q1R^m#_C`Q.../...g...t071h44b10309
20251215104239	OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,psR^m_C`Q.../...g...t049h48b10310Peter Groß-Enzersdorf * ADL329
20251215105239	OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,pmR^lh_C_Q.../...g...t056h44b10308
20251215120713	OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,rJR^lW_C`Q.../...g...t069h39b10301
20251215132852	OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,ptR^lo_C`Q.../...g...t070h42b10295
20251215142059	OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,p`R^la_C`Q.../...g...t070h42b10295
20251215143059	OE3PYC-7>APLRT1,WIDE1-1,qAR,OE3PYC-10:=/6,q!R^lc_C`Q.../...g...t071h42b10295