A total of 250 recevied packets have been found for station/object EW5967 between 06/17/2025 9:18:45 AM+00:00 and 06/20/2025 9:18:45 AM+00:00.
Request took 0.013 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 250 packets.
[>] 06/20/2025 9:15:03 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200915z3611.71N/11520.43W_231/005g013t083r000p000P000h16b09960L....DsIP
[>] 06/20/2025 9:01:00 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200900z3611.71N/11520.43W_224/006g014t083r000p000P000h16b09961L....DsIP
[>] 06/20/2025 8:50:58 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-4:@200850z3611.71N/11520.43W_210/006g013t084r000p000P000h14b09960L....DsIP
[>] 06/20/2025 8:40:55 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200840z3611.71N/11520.43W_216/006g010t084r000p000P000h14b09962L....DsIP
[>] 06/20/2025 8:30:57 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200830z3611.71N/11520.43W_216/006g014t085r000p000P000h13b09962L....DsIP
[>] 06/20/2025 8:25:52 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-4:@200825z3611.71N/11520.43W_234/008g014t085r000p000P000h13b09962L....DsIP
[>] 06/20/2025 8:20:50 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200820z3611.71N/11520.43W_262/008g015t085r000p000P000h13b09962L....DsIP
[>] 06/20/2025 8:10:48 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-4:@200810z3611.71N/11520.43W_241/005g012t085r000p000P000h13b09964L....DsIP
[>] 06/20/2025 7:50:44 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200750z3611.71N/11520.43W_250/009g020t086r000p000P000h13b09965L....DsIP
[>] 06/20/2025 7:40:42 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200740z3611.71N/11520.43W_256/007g013t086r000p000P000h13b09966L....DsIP
[>] 06/20/2025 7:35:40 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200735z3611.71N/11520.43W_261/005g015t086r000p000P000h13b09967L....DsIP
[>] 06/20/2025 7:00:36 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-4:@200700z3611.71N/11520.43W_242/007g013t087r000p000P000h14b09969L....DsIP
[>] 06/20/2025 6:20:32 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200620z3611.71N/11520.43W_219/004g017t088r000p000P000h15b09968L....DsIP
[>] 06/20/2025 6:15:29 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200615z3611.71N/11520.43W_238/005g017t088r000p000P000h14b09968L....DsIP
[>] 06/20/2025 6:05:29 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200605z3611.71N/11520.43W_236/007g018t089r000p000P000h14b09967L....DsIP
[>] 06/20/2025 6:00:44 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200600z3611.71N/11520.43W_241/006g014t089r000p000P000h13b09968L....DsIP
[>] 06/20/2025 5:55:27 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200555z3611.71N/11520.43W_246/006g011t090r000p000P000h12b09968L....DsIP
[>] 06/20/2025 5:40:26 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-4:@200540z3611.71N/11520.43W_264/006g013t090r000p000P000h12b09967L....DsIP
[>] 06/20/2025 5:15:25 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200515z3611.71N/11520.43W_228/005g010t090r000p000P000h13b09970L....DsIP
[>] 06/20/2025 4:45:23 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200445z3611.71N/11520.43W_183/005g010t090r000p000P000h10b09968L....DsIP
[>] 06/20/2025 4:20:21 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200420z3611.71N/11520.43W_181/007g012t091r000p000P000h10b09965L....DsIP
[>] 06/20/2025 4:15:22 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-4:@200415z3611.71N/11520.43W_179/005g010t091r000p000P000h10b09965L....DsIP
[>] 06/20/2025 4:10:22 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-4:@200410z3611.71N/11520.43W_193/004g009t091r000p000P000h10b09966L....DsIP
[>] 06/20/2025 4:05:21 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200405z3611.71N/11520.43W_173/006g011t092r000p000P000h10b09965L....DsIP
[>] 06/20/2025 3:50:20 AM+00:00:
EW5967>APRS,TCPXX*,qAX,CWOP-3:@200350z3611.71N/11520.43W_166/004g010t093r000p000P000h09b09964L....DsIP
* 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.