- Communications satellite
- NORAD 14421
- 1983-105A
- Inclined geosynchronous
Current orbit
View on live mapOrbit began over the Indian Ocean
Orbit ends over the Indian Ocean
Sunlit since
Enters the Earth’s shadow
In view from you
Nobody watches INTELSAT 507 go over, but a receiver still asks whether it is above the horizon. Say where you are and this card answers.
Your position is rounded to about a kilometre and sent only to the Orbinauts API, to find the pass.
No brightness has been published for INTELSAT 507, so it is not a naked-eye satellite and no city page carries pass times for it. Nothing here estimates one.
Seeing it
There is nothing to go outside for: it is too faint for the naked eye. What reaches you from it reaches a dish or an antenna, not an eye.
Timeline
- Launch
Launched, on the day GCAT records. Source
Summary
Over the Gulf of Thailand LIVE
Where is INTELSAT 507?
At 5:40:31 PM UTC INTELSAT 507 was over the Gulf of Thailand (11.8° N, 101.9° E), 35,953 km up, moving at 3.07 km/s and in sunlight.
What is INTELSAT 507?
A communications satellite in an inclined geosynchronous orbit, in space since Oct 19, 1983.
Can I see INTELSAT 507?
No, not with the naked eye: no brightness has been published for INTELSAT 507, and nothing here estimates one; the dishes and receivers on the ground use its signals instead.
General
- Operator
- INTELSAT
- State
- International Telecommunications Satellite Organization
- Built by
- Ford Aerospace, Palo Alto
- What it is
- Communications satellite
- Launched
- Mass
- 946 kg
- Operating
- Orbit class
- Inclined geosynchronous
From GCAT, Jonathan McDowell’s general catalogue, licensed CC BY 4.0: the operator, the state, the manufacturer, what it is for, the launch day, the mass, and whether it is operating. The orbit class is read from its current elements.
Latest orbital data
- Position received
- 5:40 PM UTC
- Station time (UTC)
- 5:40 PM UTC
- Latitude / longitude
- 11.8° N, 101.9° E
- Altitude
- 35,953 km
- Speed
- 3.07 km/s (11,048 km/h)
- Course
- north-east
- Light
- In sunlight until 4:39 PM UTC
- Inclination
- 11.8°
- Orbital period
- 1,444.5 minutes
- Orbits per day
- 1
- This orbit
- 35,947 to 35,955 km
- In shadow
- 55 minutes of each orbit
- In view from
- Within 7,950 km of the point below it
- Elements epoch
- Nov 7, 2026, 11:28 PM, 18 hours old
- Source
- Position from Space-Track orbital elements of Nov 7, 2026, 11:28 PM, 18 hours old.
No operator publishes an ephemeris for INTELSAT 507, so every position here comes from its orbital elements.
In orbit
- Close approaches
- No close approach to INTELSAT 507 has been reported publicly in the past thirty days.
From Space-Track’s public conjunction messages; the latest report was issued Nov 8, 2026, 1:11 PM, 3 hours old. Only approaches serious enough to be reported publicly are listed: within three days and, for two bodies near the Earth, closer than a kilometre with a chance of a collision above 1 in 10,000, the level at which NASA moves the ISS.
Beside the others
| Satellite | Typical altitude | Orbital period | Mass | In space since |
|---|---|---|---|---|
| INTELSAT 507 | 35,947 to 35,955 km | 1,445 minutes | 946 kg | 1983 |
| Hispasat 30W-6 | 35,786 to 35,786 km | 1,436 minutes | about 6.1 t | 2018 |
| Amazonas Nexus | 35,786 to 35,786 km | 1,436 minutes | about 4.1 t | 2023 |
| ARSAT-1 | 35,786 to 35,786 km | 1,436 minutes | about 3 t | 2014 |
| Astra 1N | 35,786 to 35,786 km | 1,436 minutes | about 5.3 t | 2011 |
| Hotbird 13F | 35,786 to 35,786 km | 1,436 minutes | about 4.5 t | 2022 |
Data and API
The current elements from Space-Track as an OMM object, epoch Nov 7, 2026, 11:28 PM, 18 hours old.
{
"OBJECT_NAME": "INTELSAT 507",
"OBJECT_ID": "1983-105A",
"EPOCH": "2026-11-07T23:28:48.658080",
"MEAN_MOTION": 0.99691386,
"ECCENTRICITY": 0.00010081,
"INCLINATION": 11.8011,
"RA_OF_ASC_NODE": 330.1965,
"ARG_OF_PERICENTER": 228.6969,
"MEAN_ANOMALY": 304.0627,
"EPHEMERIS_TYPE": 0,
"CLASSIFICATION_TYPE": "U",
"NORAD_CAT_ID": 14421,
"ELEMENT_SET_NO": 999,
"REV_AT_EPOCH": 13866,
"BSTAR": 0,
"MEAN_MOTION_DOT": -0.00000237,
"MEAN_MOTION_DDOT": 0
}