A total of 152 recevied packets have been found for station/object LKCS between 08/23/2025 2:24:04 AM+00:00 and 08/26/2025 2:24:04 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 152 packets.
[>] 08/26/2025 2:02:30 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *260200z4856.78N/01425.65E_220/003g...t046h81b10160>08/05 (METAR)
[>] 08/26/2025 1:32:24 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *260130z4856.78N/01425.65E_000/002g...t046h81b10160>08/05 (METAR)
[>] 08/26/2025 1:02:37 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *260100z4856.78N/01425.65E_000/000g...t050h76b10160>10/06 (METAR)
[>] 08/26/2025 12:33:03 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *260030z4856.78N/01425.65E_000/002g...t050h76b10160>10/06 (METAR)
[>] 08/26/2025 12:02:30 AM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *260000z4856.78N/01425.65E_210/002g...t050h76b10160>10/06 (METAR)
[>] 08/25/2025 11:33:04 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252330z4856.78N/01425.65E_200/003g...t050h76b10160>10/06 (METAR)
[>] 08/25/2025 11:02:37 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252300z4856.78N/01425.65E_200/003g...t052h71b10160>11/06 (METAR)
[>] 08/25/2025 10:32:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252230z4856.78N/01425.65E_210/003g...t052h71b10160>11/06 (METAR)
[>] 08/25/2025 10:03:04 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252200z4856.78N/01425.65E_210/003g...t052h71b10160>11/06 (METAR)
[>] 08/25/2025 9:32:23 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252130z4856.78N/01425.65E_000/002g...t054h66b10160>12/06 (METAR)
[>] 08/25/2025 9:03:04 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252100z4856.78N/01425.65E_180/003g...t054h66b10160>12/06 (METAR)
[>] 08/25/2025 8:32:23 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252030z4856.78N/01425.65E_000/002g...t054h66b10160>12/06 (METAR)
[>] 08/25/2025 8:03:04 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *252000z4856.78N/01425.65E_200/005g...t055h62b10160>13/06 (METAR)
[>] 08/25/2025 7:32:22 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251930z4856.78N/01425.65E_280/006g...t057h54b10160>14/05 (METAR)
[>] 08/25/2025 7:02:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251900z4856.78N/01425.65E_290/008g...t063h45b10160>17/05 (METAR)
[>] 08/25/2025 6:32:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251830z4856.78N/01425.65E_270/007g...t059h54b10160>15/06 (METAR)
[>] 08/25/2025 6:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251800z4856.78N/01425.65E_260/005g...t063h48b10160>17/06 (METAR)
[>] 08/25/2025 5:32:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251730z4856.78N/01425.65E_240/005g...t064h48b10160>18/07 (METAR)
[>] 08/25/2025 5:02:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251700z4856.78N/01425.65E_000/002g...t070h40b10160>21/07 (METAR)
[>] 08/25/2025 4:33:03 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251630z4856.78N/01425.65E_000/001g...t070h35b10160>21/05 (METAR)
[>] 08/25/2025 4:02:38 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251600z4856.78N/01425.65E_010/003g...t072h33b10160>22/05 (METAR)
[>] 08/25/2025 3:32:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251530z4856.78N/01425.65E_090/003g...t073h31b10160>23/05 (METAR)
[>] 08/25/2025 3:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251500z4856.78N/01425.65E_090/006g...t072h33b10170>22/05 (METAR)
[>] 08/25/2025 2:32:31 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251430z4856.78N/01425.65E_120/005g...t072h30b10170>22/04 (METAR)
[>] 08/25/2025 2:02:30 PM+00:00:
OK1COM-10>APZM4A,TCPIP*,qAC,T2CZECH:;LKCS *251400z4856.78N/01425.65E_000/003g...t072h33b10170>22/05 (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.