A total of 267 recevied packets have been found for station/object DG7FDL-7 between 1777296331 and 1777555531.
Request took 0.003 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 267 packets.
[>] 1777555197: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t067h25b10293LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777552489: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t068h26b10298LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777551588: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t068h26b10299LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777549785: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t066h26b10302LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777548885: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t065h27b10302LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777547085: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t064h26b10305LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777546185: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t064h27b10307LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777544385: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t064h27b10308LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777543485: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t064h27b10309LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777542585: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t064h27b10310LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777541685: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t065h28b10311LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777540785: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t065h28b10313LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777539885: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t065h28b10313LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777538988: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t065h28b10314LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777538084: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t066h29b10315LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777537196: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t067h28b10317LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777536288: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t068h27b10319LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777535377: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t066h29b10318LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777534489: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t064h29b10319LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777533580: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t064h30b10319LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777532677: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t062h32b10320LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777531792: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t062h32b10320LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777530878: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t062h31b10320LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777529977: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t063h32b10320LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1777529077: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t063h32b10320LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
* 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.
Link directly to this page:
After more than a month of development, the fourth major update of the site has launched! This update is unique from the past updates as it brings only a few new features but more than 50 bug fixes.
While short on new features, it includes the very first top-down re-write of the web app code since it was first created. One new feature that should be useful is "Track My Location".
Track My Location periodically updates a special marker shown on the map with the location reported by the web browser. The location icon in the top right corner will turn red to indicate that your location is being tracked. For registered guests, this feature can be set to turn on automatically when visiting the site.
This release brings a total of 6 new map overlaps to OpenStreetMaps to help with that. This includes hiking and cycling trails, mountain bike trails, ski slopes, even railroads and Sea maps! These crowd-sourced map overlays are available for Leaflet (OpenStreetMaps) only.
Read about all of the changes in the what's new section.
As with any major software update, there will likely be bugs that haven't been caught in testing. Please contact us to share feedback or report problems.