Does anyone know anything about 56994 - 2023-084BW? It seems to be nonexistent in the recent celestrak listings. Can someone assign 56231 (BQ) to ROM-2 instead? It is pretty close to MRC-100 and pretty close to URESAT-1, so maybe it is ROM-2(?)
1 Like
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update |
|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | ||||||
| URESAT-1 | 56992 | - | YES | YES | Identified, here are the ikhnos results | |
| ION SCV-011 | 56957 | - | YES | YES | Identified, here are the ikhnos results | |
| MRC-100 | 56993 | - | YES | YES | Identified, here are the ikhnos results | |
| SpeiSat | 56991 | - | YES | YES | Identified, here are the ikhnos results | |
| 99187 | ROM-2 | 56231 | 56226-56229,56230,56989-56991 | NO | YES | Randomly change to follow 56231, other possible 56226-56229,56230, 56989-56991 |
| 99115 | FOSSASAT-FEROX 14 - PlatziSat-1 | - | all | NO | YES | Received according to tinygs |
| 99114 | FOSSASAT-FEROX 15 | - | all | NO | YES | Received according to tinygs |
| 99112 | FOSSASAT-FEROX 17 | - | all | NO | YES | Received according to tinygs |
| 99097 | MDQSAT-1C | - | all | NO | YES | Received according to tinygs |
| 99096 | MDQSAT-1D | - | all | NO | YES | Received according to tinygs |
| RECEIVED | ||||||
| GHOST-3 | 56958 | - | YES | Identified via space-track.org | ||
| Otter Pup | 56933 | - | YES | YES | Identified, here are the ikhnos results | |
| AII-DELTA (Transporter 8 Satellite E) | 56987 | - | YES | YES | Identified, here are the ikhnos results | |
| AFR-1 (Transporter 8 Satellite D) | 56964 | - | YES | YES | Identified, here are the ikhnos results | |
| Tomorrow-R2 (Transporter 8 Satellite B) | 56962 | - | YES | YES | Identified, here are the ikhnos results | |
| GEISAT PRECURSOR (Transporter 8 Satellite A) | 56934 | - | YES | YES | Identified, here are the ikhnos results | |
| 99078 | Transporter 8 Satellite F | 56936 | 56935 | NO | YES | Received again, changed to follow 56936, removed other possible 56932-56934, 56937, 56939-56944, other possible 56935 |
| NOT RECEIVED | ||||||
| OUTPOST MISSION 1 | 56226 | - | YES | YES | Identified via space-track.org | |
| QPS-SAR-6 | 56951 | - | YES | YES | Identified via space-track.org | |
| AFRL-XVI | 56942 | - | YES | YES | Identified via space-track.org | |
| Droid.001 | 56965 | - | YES | YES | Identified via space-track.org | |
| EIVE | 56937 | - | YES | YES | Identified via space-track.org | |
| PHOTON-04(Winnebago-1) | 56959 | - | YES | YES | Identified via space-track.org | |
| GREGOIRE | 56946 | - | YES | YES | Identified via space-track.org | |
| MuSat-1 | 56967 | - | YES | YES | Identified via space-track.org | |
| Blackjack Aces-1 | 56956 | - | YES | YES | Identified via space-track.org | |
| Blackjack Aces-2 | 56955 | - | YES | YES | Identified via space-track.org | |
| Blackjack Aces-3 | 56950 | - | YES | YES | Identified via space-track.org | |
| Blackjack Aces-4 | 56952 | - | YES | YES | Identified via space-track.org | |
| 99113 | FOSSASAT-FEROX 16 | - | - | NO | YES | |
| 99095 | Pleiades-Squared | - | - | NO | YES | |
| 99192 | Istanbul | 56228 | 56226,56227,56229-56231,56989-56991 | NO | YES | Randomly change to follow 56228, other possible 56226,56227,56229-56231,56989-56991 |
| 99099 | SATLLA-2I | 56227 | 56226,56228-56231,56989-56991 | NO | YES | Randomly change to follow 56227, other possible 56226,56228-56231,56989-56991 |
| 99105 | Orbiter SN3 | - | - | NO | YES |
Dear All,
We are still not getting signal from ISTANBUL;s main beacon on 400 MHz, most probably we might have an issue with antenna deployment or the RTX module on OBC (OBS itself is alive).
As an emergency mode, after not being commanded from ground station, the satellite get into emergency beacon mode and transmitting TINY Beacon messages using its all transmitters, where the satellite has a 868 MHz LORAWAN beacon transmitter.
According to LORAWAN network we are getting signals from the satellite for the last 2 months on 868 MHz LORAWAN, but still no sign on 400 MHz.
We did an analysis on LORAWAN receptions from different LORAWAN gateways and we pretty sure ISTANBUL is Object BP.
I am attaching the analysis of last week to show how we came to conclusion that ISTANBUL is Object B.
I will be happy to hear your comments on this analysis, and also I would like to know what should be the next step to IDENTIFY and CLASIFY ISTANBUL satellite as Object BP on database/catalog.
Thanks
Baris DINC
OH2UDS/TA7W
ISTANBUL_HeliumNW_TLE analysis.pdf (635.5 KB)
Hello Baris,
Could you share some additional details, such as the frequency? Is it on 868.1 or 867.5? As well as Spreading Factor, Coding Rate, and Bandwidth?
1 Like
Sorry for late answer,
frequency is 867.9 and SF9
Looks like we have had some success with reception, thanks to K4KDR for the help!
https://nitter.net/scott23192/status/1708392293680472282
1 Like
56954 might have been identified.
which only had one match , shift D’d to the best center of the signal, leads to :
Let’s check if another one matches too.
That’s sad … Arrange a pickup with a space shuttle…
1 Like
56954 Confirmed on next day pass and added to DB
Interesting post showed up today (14-Aug-2024 UTC):
3 Likes
Wondering if any of the missions was to separate in two parts, it needs some checking. 
1 Like
It’s not matching any of my unid’d 2265 MHz obs 
Might have an ID on 56988 AYRIS-1
2 Likes