A total of 615 recevied packets have been found for station/object EL-OE3XNR between 08/26/2025 3:12:30 AM+00:00 and 08/29/2025 3:12:30 AM+00:00.
Request took 0.011 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 615 packets.
[>] 08/29/2025 3:11:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 3:09:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 3:01:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 2:59:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 2:51:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 2:49:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 2:41:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 2:39:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 2:31:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 2:29:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 2:21:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 2:19:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 2:11:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 2:09:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 2:01:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 1:59:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 1:51:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 1:49:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 1:41:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 1:39:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 1:31:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 1:29:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 1:21:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
[>] 08/29/2025 1:19:48 AM+00:00:
OE3XNR>APRS,TCPIP*,qAC,T2POLC:;EL-OE3XNR*111111z4811.40NE01446.70E0438.875MHz T000 R12k R79 Nebelstein
[>] 08/29/2025 1:11:39 AM+00:00:
EL-OE3XNR>RXTLM-1,TCPIP,qAR,OE3XNR::EL-OE3XNR:UNIT.RX Erlang,TX Erlang,RXcount/10m,TXcount/10m,none1,STxxxxxx,logic
* 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...