Soyuz-2.1b/Fregat - Ionosfera-M 3&4 - Vostochny - 25 July 2025 (05:54 UTC)

TLE for INNOSAT3

INNOSAT3
1 98553U          25207.49956303  .00000000  00000-0  50000-4 0    07
2 98553  97.4100 171.9996 0008420  52.2001 355.5076 15.21424471    01
4 Likes

tinyGS.com has added the 4 new objects from my work trying to locate & decode the new CSTP-4.x sats.

All 4 immediately started logging decodes from stations in the footprint!

10 Likes

@geoscan How stable is the GEOSCAN-x LO, new observed value 435.972200 ?

My SDR isn’t GPS locked but the frequency difference I see at the moment is to much to be caused by the sdr LO.

GEOSCAN-1
1 98559U          25207.63245003  .00000000  00000-0  16318-2 0    09
2 98559  97.4100 173.0234 0016147 141.4184 269.7200 15.21985603    07

3 Likes

Frequency 436.163100

GEOSCAN-2
1 98558U          25207.56703300  .00000000  00000-0  24756-1 0    03
2 98558  97.4100 172.9467 0011560  49.4078   5.0868 15.22043063    02

3 Likes

GEOSCAN-x LO should be not more than couple of kHz. I guess frequency values you provided might be actual and caused by medium

1 Like

Thanks for the update, I guess that is the reason why concatenating the data is problematic.

I will try to get better results but to be honest it is difficult.

Jan | PE0SAT

2 Likes

New Image Transmitted From INNOSAT16, now in better resolution. But there is still no Earth

5 Likes

Contacted the strf creator @cgbsat

At 436MHz, a 1000Hz offset corresponds to 0.7 km/s in velocity. Since that’s about 10% of orbital velocity I would think that will make TLE fitting infeasible.

But you can fit each curve separately and apply an offset to each.

Lets see if we can find an offset.

Jan | PE0SAT

4 Likes

Ref. the CSTP-4.x satellites, after the tinyGS.com administrator added those objects to his database and decodes started coming in, he determined that the telemetry appeared to match up w/ the format seen in the CSTP-1.x & CSTP-2.x sats.

I thought it was cool to see the transition where he started applying the decoder to received frames:

2 Likes

GNSS corrected TLE’s

INNOSAT16
1 98552U          25209.47340000  .00000000  00000-0  50000-4 0    07
2 98552  97.2801 175.9015 0009866 108.2683 295.3575 15.21172526    01

3 Likes

These will not be perfect, the LO drift makes fitting difficult.

239ALFEROV
1 98560U          25210.14500129  .00000000  00000-0  22649+0 0    05
2 98560  97.2801 174.3136 0009866 108.2683  19.3901 15.24288825    07
GEOSCAN-1
1 98559U          25210.14518985  .00000000  00000-0  24746-2 0    05
2 98559  97.4100 175.0854 0011560  49.4078  78.2838 15.21244438    04
GEOSCAN-2
1 98558U          25210.14421699  .00000000  00000-0  11151-1 0    04
2 98558  97.4200 176.1508 0021954 111.1616  16.8002 15.23828294    06
GEOSCAN-3
1 98557U          25210.20804363  .00000000  00000-0  50000-4 0    02
2 98557  97.4100 177.8394 0011560  49.4078  71.7190 15.15409510    07
GEOSCAN-4
1 98556U          25210.20885421  .00000000  00000-0  12132+1 0    05
2 98556  97.4100 177.5378 0011560  49.4078  73.4358 15.16363346    07
GEOSCAN-5
1 98555U          25210.20885421  .00000000  00000-0 -13507+1 0    02
2 98555  97.4100 176.0247 0011560  49.4078  73.3481 15.14704834    00
GEOSCAN-6
1 98554U          25210.14525865  .00000000  00000-0 -28825-2 0    08
2 98554  97.4100 175.3038 0008420  52.2001  75.5472 15.21470362    06
INNOSAT3
1 98553U          25210.20834735  .00000000  00000-0  12477-1 0    07
2 98553  97.4100 175.2603 0008420  52.2001  70.1408 15.23624243    03
INNOSAT16
1 98552U          25210.21147922  .00000000  00000-0 -10476-1 0    00
2 98552  97.2801 176.7763 0009866 108.2683  14.1027 15.20057854    04
4 Likes

Sorry, but it seems these are already pretty off

1 Like

INNOSAT16 new TLE

INNOSAT16
1 98552U          25211.73718750  .00000000  00000-0  50000-4 0    00
2 98552  97.4100 177.3817 0015621 342.3901 209.9746 15.19739116    03

1 Like

There should not be a plus here, because of this the PstRotator crashing.

3 Likes

Confirming.
Gpredict also crashes for GEOSCAN-4 and -5 (with +1).
The other GEOSCAN TLEs (with -1) are working.

1 Like

A TLE for Geoscan-4, it may be not so accurate as it was produced using old observations:

GEOSCAN-4
1 98556U          25211.39511701  .00000000  00000-0  82229-4 0    01
2 98556  97.4100 177.0420 0014369  56.1820  83.7452 15.22104405    05
2 Likes

And one TLE for Geoscan-5, again it is not very accurate but it seems better that the one we have now:

GEOSCAN-5
1 98555U          25209.47968711  .00000000  00000-0  50000-4 0    05
2 98555  97.4200 173.1826 0016821  52.9234  38.4392 15.23975807    03
3 Likes

Better TLE’s for 239ALFEROV

239ALFEROV
1 98560U          25209.47548935  .00000000  00000-0  50000-4 0    03
2 98560  97.4200 179.1219 0022354  94.9108 329.0355 15.20786303    01
3 Likes

Updated TLE

INNOSAT16
1 98552U          25213.55310750  .00000000  00000-0  50000-4 0    00
2 98552  97.4100 179.1269 0015621 170.1161 240.5242 15.05926634    09
INNOSAT3
1 98553U          25213.48350990  .00000000  00000-0  50000-4 0    03
2 98553  97.4100 183.2665 0009200  93.8092 329.1810 15.20742872    08
GEOSCAN-6
1 98554U          25213.48291530  .00000000  00000-0  50000-4 0    08
2 98554  97.4200 175.1819 0021909  71.4167 332.8198 15.06426376    08
2 Likes

Were there successful observations after this TLE update for GEOSCAN-5?