Sleipner Vest

Transport according to Sodir's field description

The well stream is sent to the Sleipner A facility for processing. Sales gas is exported from Sleipner A via Gassled (Area D) to the market. Unstable condensate is transported in a pipeline to the Kårstø terminal.

Quoted from Sodir's field description, updated 20 Feb 2026. Sodir, field description

Notes

• Gas is mixed in the pipeline network. A «possible route» is a pipeline connection onwards from a junction or an onshore plant, not a measure of where the field's gas actually goes.
• The arrows show direction, not volume. The direction is Sodir's from → to for each pipeline; Sodir has no flow per pipeline.

Rigs

Pipeline systems and plants

Pipeline systems and plants (TUF) that the field's pipelines belong to or that the production continues into, with the owners. “Onward” means that the production continues into it. The link comes from the pipelines in the map above.

Fleet

Rigs drilling, offshore vessels at the facilities in the AIS picture 7 Oct 2026, 14:34 UTC and the supply vessels from the base in the last 30 days.

Rigs

Norwegian Offshore Directorate, exploration wells being drilled (NLOD 2.0), 7 Oct 2026 · Norwegian Offshore Directorate, wellbores spudded in the last 120 days (NLOD 2.0), 7 Oct 2026 · AIS from Kystverket (Norwegian Coastal Administration, Kystdatahuset real-time picture) (NLOD 1.0), 7 Oct 2026, 14:34 UTC · OESA, rig key Sodir ↔ MMSI ↔ IMO (curated: name match in AIS and SafeSeaNet, checked against the well) (NLOD 1.0 / NLOD 2.0), 7 Oct 2026

• West Elara Seadrill
  No well in the last 120 days at Sodir
  AIS 7 Oct 2026, 14:34 UTC: at Sleipner B (130 m)

Visits, latest day with data: 1 Oct

Rigs and offshore vessels that lay within 2 km of a facility at under 1 knot for at least 30 minutes, according to the AIS positions for 1 Oct 2026 from the Norwegian Coastal Administration. Kystdatahuset publishes the history about a week late. A visit shows that the vessel was there, not who it worked for. AIS from Kystverket (Norwegian Coastal Administration, Kystdatahuset historical positions) (NLOD 1.0), latest day 1 Oct 2026 · Norwegian Coastal Administration, Kystdatahuset: register type (SafeSeaNet) (NLOD 1.0), 1 Oct 2026 · Norwegian Offshore Directorate, facilities with position (NLOD 2.0), 7 Oct 2026 · OESA, rig key Sodir ↔ MMSI ↔ IMO (curated) (NLOD 1.0 / NLOD 2.0), 7 Oct 2026

No rigs or offshore vessels lay at the facilities in the period.

Method: A visit is a continuous stay within 2 km of a facility at under 1 knot for at least 30 minutes, computed from the AIS positions. Gaps in the data of up to 60 minutes, or 3 hours when the vessel is in the same place before and after, do not count as interruptions. Hours are the sum of the visits. Only rigs and vessels with an offshore register type or registered with the Norwegian Offshore Directorate are included.

Supply vessels from the base, last 30 days

Reported departures by offshore vessels (register type in SafeSeaNet). Supply base: Norwegian Offshore Directorate (the field's main supply base); the port's position from the World Port Index, Wikidata or OpenStreetMap (NLOD 2.0 / offentlig eiendom / ODbL), 28 Sep 2026 · Norwegian Coastal Administration, Kystdatahuset: reported voyages and register type (SafeSeaNet) (NLOD 1.0), 6 Oct 2026

• Dusavik 17 offshore vessels, 72 departures
  Most departures: Sygna Tide 11, Rem Crusader 10, Skandi Flora 10, Juanita 9, Edda Fram 8

Who charters a rig or vessel, and at what rate, is not in open data. A vessel is linked to a field only when AIS shows it within 2 km of one of the field's own facilities or its host facility, at under 1 knot – that says the vessel was there, not who it works for. Facilities on the export route do not count. Tankers loading oil from production ships (FPSOs) and loading buoys are not included. Supply vessels per base are based on reported departures (SafeSeaNet). The destination is usually just the sea area (“Offshoreinst. Nordsjøen”, “… Barentshavet”), so the field the vessel supplies is not stated. Peterhead is British and has no departures in Kystdatahuset. AIS coverage offshore varies. A vessel without positions for a period may have been there without being recorded. Ship data: Norwegian Coastal Administration. Not for navigation.

Sources

All figures and links on the page come from these sources. Curated links are entered by hand by OESA from the source text, and the quote is checked against the source at every build.

• ENTSOG Transparency Platform, entry points for Norwegian gas (the points in OESA's gas panel); position from the Norwegian Offshore Directorate 7 Oct 2026
• OESA, pipeline graph derived from Sodir pipelines and facilities (merging ≤0.8 km, tee ≤4 km, branch ≤1 km) 7 Oct 2026Pipelines are linked on the Sodir facility ids. Pipeline ends without a continuation are linked into the nearest pipeline with the same medium within 4 km.
• Norwegian Offshore Directorate, wellbores with drilling facility (spudded in the last three years) 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, licensees per field (current shares) 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, fields: status, operator and supply base 28 Sep 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, mobile facilities (responsible company and Acknowledgement of Compliance) 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, facilities 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, marketable production per field and month 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, reserves per field 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, transport pipelines 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, owners and operators of pipeline systems and plants (TUF) 7 Oct 2026 · licence NLOD 2.0
• Norwegian Offshore Directorate, field description Sleipner Vest (Transport), curated by OESA 20 Feb 2026 · licence NLOD 2.0

Not in the data: Flow in each pipeline, which field's gas ends up in which country, and the buyers of oil and gas. Gas is mixed in the network, so a “possible route” is a pipeline connection, not measured flow.