From these TLEs, KOSTKA is probably object BU - 69935, with alternatives 69936 and 69938.
Also KOSTKA will transmit additional periodic CWs over Europe today at 23:25-23:40 UTC.
4 Likes
Based on 2026-156:
KOSTKA: 69935
Alternative:
69936: 0.207 kHz 436.870805 MHz | TBA - TO BE ASSIGNED
Jan | PE0SAT
4 Likes
Based on 2026-156:
Unknown: 69907 (one of the Satellites on 435.600)
Alternatives:
69906: 0.161 kHz 435.600293 MHz | TBA - TO BE ASSIGNED
69910: 0.164 kHz 435.600324 MHz | TBA - TO BE ASSIGNED
Jan | PE0SAT
3 Likes
3 Likes
Hi from the Apolink Team,
We are currently tracking 88210:
1 88210U 26201.55979506 .00001720 00000-0 17802-3 0 0044
2 88210 97.7548 101.7921 0006594 96.3992 263.7977 14.91339137001973
If we could get new contacts for this, that would be great!
Still on the search, nothing yet. But this TLE is based on the celestrak post above for object J.
Best,
-The Apolink Team
Can someone help us updating our TLE to object 88210?
@fredy Are you able to help or contact someone who can ?
1 Like
If Object 88210 (space-track TLE file) is now:
space-track.org: TRANSPORTER-17 OBJECT J, 2026-156J (International Designator), 69877 (NOARD ID), then here’s the latest TLE:
1 69877U 26156J 26204.44487355 .00002979 00000-0 30412-3 0 9991
2 69877 97.7541 104.6287 0006612 89.3439 270.8537 14.91356597 2409
SENTINEL-1 (SatNOGS 98261)
So far we had no luck contacting (DL TLM or UL CMD) to our satellite at our Astralintu GS (Ecuador, Quito). We have been tracking it and using TLE per space-track TLE file (under object 88262). Since space-track issued NOARD IDs for the TR-17 75 “2026-156” satellites/objects, we switched to tracking it under:
88207, TRANSPORTER-17, OBJECT F, 2026-156F, 69874 w/ TLE:
1 69874U 26156F 26204.18153855 .00001504 00000-0 15820-3 0 9993
2 69874 97.7520 104.3528 0004724 80.6591 279.5161 14.90867520 2369
But still no luck. I’m attaching here the GRC file (used by Astralintu GS and we tested it to check that our Yamcs-based SW works, receiving TLM/beacon messages and uploading commands).
Note: I added the extension “.txt” to the GRC file “sentinel_final_ver01.grc” to allow it to pass through your “upload file filter.”
sentinel_final_ver01.grc.txt (68.6 KB)
flowgraph_output.txt (5.1 KB)
1 Like
Sorry - can you please clarify?
So you ARE receiving downlink packets on 402.000 MHz?
What modes / frequencies are you NOT receiving?
Thanks!
Our Astralintu GS is tuned to 402.000 MHz, but we are not receiving any DL packets and we don’t know if our UL commands are reaching the satellite (since we don’t receive back the beacon message that’s supposed to come down in response to the UL command).
1 Like
Oh sorry! I see the confusion I created by attaching this flowgraph_output.txt file and not explaining it. This file is generated from our factory SW testing using Yamcs SW and SDR (https://www.ettus.com/all-products/usrp-b200mini/) attached to Linux box.
2 Likes
Had you seen this SatNogs observation? There is a single decode that begins with “C4” which resembles your test decodes.
Per previous posts, I’ve changed in DB IPoS-TDsM to follow 69877 and Sentinel-1 to follow 69874. In the next couple of hours the TLE will be updated in both Network and DB.
Unfortunately due to other tasks (LSF’s PHASMA mission and Network development) I didn’t make it to perform any analysis until now on the published TLE. I’ll try today and during the weekend.
From the size and the lack of any signal in the waterfall I’ll guess that this is a noise frame (false positive)
1 Like
Although, I can’t confirm for 100%, but based on deep-dive inspection of our SENTINEL-1 Flight SW, we should be transmitting/receiving at 402.000 MHz (not 401.025 MHz).
I’m not RF person, but I don’t think this signal is SENTINEL-1.
1 Like
Thanks Fredy. I agree.
Would you happen to know which satellite number from Celestrak and Space Track this corelates to?
Thanks,
-The Apolink team!
Hi from the Apolink Team,
Can we update our TLE to (NORAD 69916):
1 69916U 26156AZ 26205.25533484 .00002992 00000-0 30910-3 0 9998
2 69916 97.7513 105.4072 0004548 81.4287 278.7446 14.90884500 2521
Kayhan Space is helping us identify our object. So we are hoping to get good results from this TLE
Thanks!
-The Apolink Team
1 Like
Can you provide some context, please?
What is that number?