A total of 155 recevied packets have been found for station/object DG7FDL-7 between 1773129657 and 1773388857.
Request took 0.008 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 155 packets.
[>] 1773380072: DG7FDL-7>APLRG1,WIDE1-1,qAO,DB0TAW-12:=L4gu/Pv{F_ !G.../...g...t071h36b10131LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773374668: DG7FDL-7>APLRG1,WIDE1-1,qAO,DB0WK-10:=L4gu/Pv{F_ !G.../...g...t074h34b10142LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773373768: DG7FDL-7>APLRG1,WIDE1-1,qAO,DB0WK-10:=L4gu/Pv{F_ !G.../...g...t074h34b10143LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773365671: DG7FDL-7>APLRG1,WIDE1-1,qAO,DB0TAW-12:=L4gu/Pv{F_ !G.../...g...t073h38b10165LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773364762: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t075h39b10167LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773363873: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t075h39b10170LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773362962: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t074h39b10173LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773362083: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t075h39b10175LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773361165: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t075h39b10177LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773360283: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t075h39b10179LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773359362: DG7FDL-7>APLRG1,WIDE1-1,qAO,DB0TAW-12:=L4gu/Pv{F_ !G.../...g...t075h39b10180LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773358472: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t074h40b10181LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773357565: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t075h38b10183LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773356656: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t074h39b10183LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773355756: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t074h39b10185LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773354856: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t074h38b10186LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773353956: DG7FDL-7>APLRG1,WIDE1-1,qAO,DB0TAW-12:=L4gu/Pv{F_ !G.../...g...t071h41b10188LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773353056: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t068h45b10191LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773352162: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t071h43b10190LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773351256: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t072h41b10192LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773350356: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t073h40b10192LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773349456: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t075h39b10193LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773348558: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t074h39b10194LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773347656: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t073h40b10195LoRa Digi-iGate 433.775 MHz Bad Hersfeld 256m/NN
[>] 1773346756: DG7FDL-7>APLRG1,WIDE1-1,qAO,DG0OGM-10:=L4gu/Pv{F_ !G.../...g...t074h39b10196LoRa 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.