Skip to content
SatelliteIndex

Satellite · NORAD 25158 · COSPAR 1998-007B

ORBCOMM FM03

UnknownPayloadLEOIoT / M2M derived

Altitude now

—

no element set

Velocity

—

Inclination

107.96°

Period

100.3 min

100.3 min

Perigee

741km

Apogee

805km

orbit unavailableNo orbital element set on file.· Metadata updated 9 h ago

Live position

Live position

Live position unavailable — no public orbital element set exists for this object (it may be classified, untracked or too small to catalogue).

Mission

Mission & classification

Mission type derived
IoT / M2M
Object type
Payload
SATCAT ops status
Non-operational [-]
Radar cross-section
0.7 m²
Constellation membership derived
ORBCOMM via name_pattern

CelesTrak groups

Not listed in any CelesTrak group.

Aliases

  • ORBCOMM FM03Celestrak Satcat

Ownership

Operator & country

Operator
ORBCOMM
SATCAT owner code
ORB · ORBCOMM
Country
United States US

Launch

Launch

Launch page →
Launch date
10 Feb 1998
COSPAR launch id
1998-007
Launch site
Vandenberg Space Force Base (Western Range), California

Objects from the same launch · 4

Change log

History

No changes recorded since first ingestion on 11 Sept 2026 18:54 UTC. Status, orbit class, name and ownership changes are logged here as sources are re-ingested.

Regulatory

UN registration

UN Register of Objects Launched into Outer Space (UNOOSA) — connector planned, not yet ingested; registration unavailable

Transparency

Sources & provenance

All sources →

No source is linked to this record yet — the catalogue row exists but no provenance entry has been written for it.

Field provenance

No field-level provenance recorded.

Timeline

Events

All events →

No events detected for this object yet. Launches, decays and orbit changes are generated by the derived-analytics connector.

Reference

Identifiers

NORAD catalogue number
25158
COSPAR / international designator
1998-007B
SatelliteIndex id
sat_01M28X3JQ7JAY3ZRKDH046TYH7
Canonical slug
orbcomm-fm03-25158

Orbit class, mission type and constellation membership are derived by SatelliteIndex (IoT / M2M) — see the methodology. Positions are propagated estimates, not tracking measurements; never use them for conjunction assessment.