A total of 411 recevied packets have been found for station/object W1IMD between 06/17/2025 10:58:09 AM+00:00 and 06/20/2025 10:58:09 AM+00:00.
Request took 0.025 seconds to find in our database.
Packet history is available for up to 3 days. Sign up for a free account to view 30 up to days history. Use [>] to decode with our packet packet decoder tool.
Displaying 1 - 25 of 411 packets.
[>] 06/20/2025 10:50:41 AM+00:00:
W1IMD>APN391,qAR,N1QQA-10:!4350.15NS07049.05W#PHG3464 PEAKED MTN PASS
[>] 06/20/2025 10:44:42 AM+00:00:
W1IMD>BEACON,WIDE2-2,qAR,K1WH:W1IMD HIRAM, ME
[>] 06/20/2025 10:35:42 AM+00:00:
W1IMD>APN391,WIDE2-2,qAR,KA1GJU-3:!4350.15NS07049.05W#PHG3464 HIRAM ME
[>] 06/20/2025 10:20:42 AM+00:00:
W1IMD>APN391,qAR,K1WH:!4350.15NS07049.05W#PHG3464 PEAKED MTN PASS
[>] 06/20/2025 10:05:41 AM+00:00:
W1IMD>APN391,WIDE2-2,qAR,KA1GJU-3:!4350.15NS07049.05W#PHG3464 HIRAM ME
[>] 06/20/2025 9:44:42 AM+00:00:
W1IMD>BEACON,WIDE2-2,qAR,N1QQA-10:W1IMD HIRAM, ME
[>] 06/20/2025 9:35:41 AM+00:00:
W1IMD>APN391,WIDE2-2,qAR,K1WH:!4350.15NS07049.05W#PHG3464 HIRAM ME
[>] 06/20/2025 9:05:41 AM+00:00:
W1IMD>APN391,WIDE2-2,qAR,K1WH:!4350.15NS07049.05W#PHG3464 HIRAM ME
[>] 06/20/2025 8:50:41 AM+00:00:
W1IMD>APN391,qAR,N3LLO-2:!4350.15NS07049.05W#PHG3464 PEAKED MTN PASS
[>] 06/20/2025 8:44:42 AM+00:00:
W1IMD>BEACON,WIDE2-2,qAR,KA1GJU-3:W1IMD HIRAM, ME
[>] 06/20/2025 8:35:41 AM+00:00:
W1IMD>APN391,WIDE2-2,qAR,N3LEE-10:!4350.15NS07049.05W#PHG3464 HIRAM ME
[>] 06/20/2025 8:20:42 AM+00:00:
W1IMD>APN391,qAR,K1WH:!4350.15NS07049.05W#PHG3464 PEAKED MTN PASS
[>] 06/20/2025 7:50:45 AM+00:00:
W1IMD>APN391,qAR,K1WH:!4350.15NS07049.05W#PHG3464 PEAKED MTN PASS
[>] 06/20/2025 7:44:41 AM+00:00:
W1IMD>BEACON,WIDE2-2,qAR,KA1GJU-3:W1IMD HIRAM, ME
[>] 06/20/2025 7:35:41 AM+00:00:
W1IMD>APN391,WIDE2-2,qAR,KA1GJU-3:!4350.15NS07049.05W#PHG3464 HIRAM ME
[>] 06/20/2025 7:24:42 AM+00:00:
W1IMD>BEACON,WIDE2-2,qAR,N3LEE-10:W1IMD HIRAM, ME
* If you compare the raw packets with similar data from other websites it may differ (especially the path), the reason is that we are not collecting packets from the same APRS-IS servers. Each APRS-IS server performes duplicate filtering, and which packet that is considered to be a duplicate may differ depending on which APRS-IS server you receive your data from.
Snapshot Active 
Filter Active 
Map Wizard Active 
Please wait while the map is redrawn...