A total of 39 recevied packets have been found for station/object LKCS between 06/15/2025 7:09:55 PM+00:00 and 06/18/2025 7:09:55 PM+00:00.
Request took 0.01 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 39 packets.
[>] 06/18/2025 7:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181900z4856.78N/01425.65E_300/003g...t073h56b10210>23/14 (METAR)
[>] 06/18/2025 6:32:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181830z4856.78N/01425.65E_310/003g...t077h47b10210>25/13 (METAR)
[>] 06/18/2025 6:02:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181800z4856.78N/01425.65E_290/003g...t077h47b10210>25/13 (METAR)
[>] 06/18/2025 5:32:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181730z4856.78N/01425.65E_320/006g...t079h44b10210>26/13 (METAR)
[>] 06/18/2025 5:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181700z4856.78N/01425.65E_320/007g...t079h44b10210>26/13 (METAR)
[>] 06/18/2025 4:32:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181630z4856.78N/01425.65E_320/005g...t079h44b10220>26/13 (METAR)
[>] 06/18/2025 4:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181600z4856.78N/01425.65E_320/007g...t079h44b10220>26/13 (METAR)
[>] 06/18/2025 3:32:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181530z4856.78N/01425.65E_330/006g...t079h44b10220>26/13 (METAR)
[>] 06/18/2025 3:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181500z4856.78N/01425.65E_330/006g...t079h41b10220>26/12 (METAR)
[>] 06/18/2025 2:32:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181430z4856.78N/01425.65E_000/006g...t079h44b10220>26/13 (METAR)
[>] 06/18/2025 2:02:37 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181400z4856.78N/01425.65E_000/006g...t079h41b10220>26/12 (METAR)
[>] 06/18/2025 1:32:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181330z4856.78N/01425.65E_010/003g...t079h41b10220>26/12 (METAR)
[>] 06/18/2025 1:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181300z4856.78N/01425.65E_320/005g...t079h39b10220>26/11 (METAR)
[>] 06/18/2025 12:32:23 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181230z4856.78N/01425.65E_340/005g...t079h39b10220>26/11 (METAR)
[>] 06/18/2025 12:02:37 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181200z4856.78N/01425.65E_000/003g...t077h38b10230>25/10 (METAR)
[>] 06/18/2025 11:32:30 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181130z4856.78N/01425.65E_000/003g...t077h41b10230>25/11 (METAR)
[>] 06/18/2025 11:02:30 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181100z4856.78N/01425.65E_000/005g...t075h44b10230>24/11 (METAR)
[>] 06/18/2025 10:32:30 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181030z4856.78N/01425.65E_000/005g...t075h50b10230>24/13 (METAR)
[>] 06/18/2025 10:02:37 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *181000z4856.78N/01425.65E_000/005g...t075h50b10230>24/13 (METAR)
[>] 06/18/2025 9:32:31 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *180930z4856.78N/01425.65E_000/002g...t073h53b10240>23/13 (METAR)
[>] 06/18/2025 9:02:45 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *180900z4856.78N/01425.65E_000/002g...t073h49b10240>23/12 (METAR)
[>] 06/18/2025 8:32:31 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *180830z4856.78N/01425.65E_000/003g...t072h56b10240>22/13 (METAR)
[>] 06/18/2025 8:02:38 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *180800z4856.78N/01425.65E_110/003g...t070h60b10240>21/13 (METAR)
[>] 06/18/2025 7:32:30 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *180730z4856.78N/01425.65E_000/002g...t068h64b10240>20/13 (METAR)
[>] 06/18/2025 7:02:31 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *180700z4856.78N/01425.65E_000/001g...t064h72b10240>18/13 (METAR)
* 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.