My identification now:
JACK-003 66655
SPIRONE 66657
JACK-004 66659
K-HERO 66660
SNUGLITE-III-B 66661
SNUGLITE-III-A 66662
5 Likes
JACK-003 not object 66655 now
1 Like
Decoded three beacons from SNUGLITE-III Hana on Duri’s frequency (436.788 MHz).
The used TLE (66661) [2025-11-30 09:15:40 UTC] led to an increasing frequency while the signal’s frequency decreased.
I did not receive any signal on Hana’s frequency (436.460 MHz).
1 Like
Also!
1 Like
What object did you use for this decode?
Object E
1 Like
Hello,
Thank you very much for your continuous support in tracking our satellite.
I am an engineer for the BEE-1000 mission.
We are currently attempting to acquire the satellite’s signal and are reviewing possible TLE candidates.
Based on the deployment sequence of KSLV-II, we initially assumed that OBJECT-L (66660) might correspond to our satellite.
However, from the information you provided earlier, it appears that this object is likely associated with another spacecraft.
Although it is still difficult to determine with certainty which object corresponds to BEE-1000, OBJECT-J (66658) now seems to be a more probable candidate. Therefore, could you please update the TLE estimation for BEE-1000 using the following OBJECT-J TLE?
1 66658U 25274J 25334.80928811 .00003235 00000-0 32015-3 0 9992
2 66658 97.7371 262.2233 0012012 323.3126 36.7270 14.92507752 628
We greatly appreciate your assistance.
(Additionally, I am attaching the deployment order of the KSLV-II CubeSats for your reference. Two satellites were deployed approximately every 20 seconds:)
- CUB01: SPIRONE & CUB02: PERSAT01
- CUB03: COSMIC & CUB04: JACK-03
- CUB05: JACK-04 & CUB06: INHA-RoSAT
- CUB07: K-HERO & CUB08: SEJONG-4
- CUB09: SNUGLITE-III & CUB10: BEE-1000
- CUB11: ETRISat
- CUB12: E3_TESTER_KARI-1
1 Like
BEE-100 changed in DB to follow 66658.
1 Like
SNUGLITE-III
A member from the team told me that Duri transmits incorrectly with Hana’s ID.
This means the frequencies are correct and the satellites can only be distinguished by its frequency.
4 Likes
4 Likes
A status update, given that the TLE are ~1-2 days old, I’m avoiding moving to identification yet, while some satellites are almost clear which object match:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Reception | Last Update |
|---|---|---|---|---|---|---|---|
| RECEIVED & DEMODULATED/DECODED | |||||||
| 98496 | SNUGLITE-III HANA | 66661 | - | - | YES | YES | Received, changed to follow 66661 |
| 98497 | SNUGLITE-III DURI | 66661 | - | - | YES | YES | Received, changed to follow 66661 |
| 98489 | K-HERO | 66660 | - | - | YES | YES | Received, changed to follow 66660 |
| 98492 | SPIRONE | 66657 | - | - | YES | YES | Received, changed to follow 66657 |
| 98490 | INHA-RoSAT | 66651 | 66650, 66652 | - | YES | YES | Received, changed to follow 66651, other candidates 66650, 66652 |
| 98487 | JACK-004 | 66659 | 66658(unlikely), 66660(unlikely) | - | YES | YES | Received, changed to follow 66659, other candidates 66658(unlikely), 66660(unlikely) |
| 98488 | JACK-003 | 66654 | 66653(unlikely), 66655 | - | YES | YES | Received, changed to follow 66654, other candidates 66653(unlikely), 66655 |
| RECEIVED | |||||||
| 98483 | CAS500-3 | 66652 | 66650(unlikely), 66651(unlikely), 66653(unlikely), 66654(unlikely), 66655(unlikely) | - | YES | YES | Received, Changed to follow 66652, other candidates 66650(unlikely), 66651(unlikely), 66653(unlikely), 66654(unlikely), 66655(unlikely) |
| UNKNOWN STATUS | |||||||
| 98491 | PERSAT01 | 66656 | 66650, 66651, 66652, 66653, 66654, 66655, 66657, 66658, 66659, 66660, 66661, 66662 | - | YES | NO | No reception, randomly changed to follow 66656 |
| 98484 | SJSAT-4 | 66650 | 66651, 66652, 66653, 66654, 66655, 66656, 66657, 66658, 66659, 66660, 66661, 66662 | - | YES | NO | No reception, randomly changed to follow 66650 |
| 98493 | BEE-1000 | 66658 | 66650, 66651, 66652, 66653, 66654, 66655, 66656, 66657, 66659, 66660, 66661, 66662 | - | YES | NO | No reception, randomly changed to follow 66658 |
| 98486 | E3_TESTER_KARI-1 | 66655 | 66650, 66651, 66652, 66653, 66654, 66656, 66657, 66658, 66659, 66660, 66661, 66662 | - | YES | NO | No reception, randomly changed to follow 66655 |
| 98485 | ETRISat | 66662 | 66650, 66651, 66652, 66653, 66654, 66655, 66656, 66657, 66658, 66659, 66660, 66661 | - | YES | NO | No reception, randomly changed to follow 66662 |
| 98494 | COSMIC | 66653 | 66650, 66651, 66652, 66654, 66655, 66656, 66657, 66658, 66659, 66660, 66661, 66662 | - | YES | NO | No reception, randomly changed to follow 66653 |
2 Likes
Hello,
First of all, thank you very much again for your continuous support in tracking the satellites.
Our teams (COSMIC & BEE) would like to share some updates.
COSMIC
We have confirmed that COSMIC is responding to our telecommands when matched with OBJECT-J (66658).
BEE-1000
For the past three passes, we have consistently succeeded in AX100 ping responses from OBJECT-B (66651).
Based on these observations, our current assessment is:
-
COSMIC → 66658
-
BEE-1000 → 66651
However, we are aware that INHA-RoSAT is also showing nominal signals on 66651, which is causing some confusion on our side as well.
For now, could you please update the TLE assignments for COSMIC and BEE-1000 to 66658 and 66651, respectively?
We will share further updates as soon as we complete more definitive signal verification.
Thank you once again for all your support.
2 Likes
Thank you for the update, I’ve just updated COSMIC and BEE-1000 to follow objects 66658 and 66651 respectively.
Later today, as we have updated TLE from space-track.org, I’m going to check them against latest observations in order to start identifying the objects of this launch.
2 Likes
Hello,
We also currently consider the likelihood of 66651 to be low. We have confirmed a response to the TC on 66652 or 66653. Could you please change our INHA-RoSAT to 66652?
Thank you as always for your help.
1 Like
Done, changes will be applied to DB and Network in the next hours.
1 Like
