25/11-5

Exploration · Appraisal · P&A · Oil · Esso Exploration and Production Norway A/S · Balder · PL 001

Everything taken from 25/11-5 that the Directorate has on file, each with its depth and the formation that depth sits in by this wellbore's own tops. Open a core for its photographs, the thin sections and slides cut from it, and the tests across it.

Cores

1 CORE · 2.1 FT IN ALL

Core	Top	Base	Depth in	In	Photos	Sample available
Core 1 →	5,654	5,661	ft	Balder Fm, Sele Fm	—	Yes

Cored length by unit, m

The core log: every core down the well →Every core from Balder →

Fluid samples

Test	Fluid	From, m	To, m	In	Tested	Received	Sample available
DST 1	—	1,750	1,765	Hermod Fm	Apr 30, 1974	Jun 21, 1991	Yes

Every fluid sample from Balder →

Geochemistry and fluid analysis on file

Geochemical information 1pdf · 815 KB

Drill-stem tests

Test	From, m	To, m	In	Choke, mm	Oil, Sm³/d	Gas, Sm³/d	Oil density, g/cm³	GOR, m³/m³	BHP, MPa	Temp, °C
DST 1	1,750	1,765	Hermod Fm	—	636	28,371	0.91	44	—	—

Every drill-stem test in Balder →

Cuttings

198.1 to 2,164.1 mSample available: no

Palynology slides

109 ON FILE · 1,726.4 TO 7,080

Made from: Ditch cuttings 83, Sidewall core 14, Core 12. Laboratory codes: none given 97, RRI 12.

Depth	Made from	Lab code	In
1,726.4 m	Core	RRI	Sele Fm
1,727.4 m	Core	RRI	Sele Fm
1,728.4 m	Core	RRI	Sele Fm
1,729.1 m	Core	RRI	Sele Fm
1,730.4 m	Core	RRI	Sele Fm
1,730.9 m	Core	RRI	Sele Fm
1,731.4 m	Core	RRI	Hermod Fm
1,731.7 m	Core	RRI	Hermod Fm
1,732 m	Core	RRI	Hermod Fm
1,732.7 m	Core	RRI	Hermod Fm
1,732.8 m	Core	RRI	Hermod Fm
2,450 ft	Ditch cuttings	—	Nordland Gp
2,480 ft	Ditch cuttings	—	Nordland Gp
2,540 ft	Ditch cuttings	—	Skade Fm
2,630 ft	Ditch cuttings	—	Skade Fm
2,720 ft	Ditch cuttings	—	Skade Fm
2,810 ft	Ditch cuttings	—	Skade Fm
2,900 ft	Ditch cuttings	—	Skade Fm
2,990 ft	Ditch cuttings	—	Skade Fm
3,080 ft	Ditch cuttings	—	Skade Fm
3,170 ft	Ditch cuttings	—	Hordaland Gp
3,260 ft	Ditch cuttings	—	Hordaland Gp
3,350 ft	Ditch cuttings	—	Hordaland Gp
3,440 ft	Ditch cuttings	—	Hordaland Gp
3,530 ft	Ditch cuttings	—	Hordaland Gp
3,620 ft	Ditch cuttings	—	Hordaland Gp
3,710 ft	Ditch cuttings	—	Hordaland Gp
3,800 ft	Ditch cuttings	—	Hordaland Gp
3,890 ft	Ditch cuttings	—	Hordaland Gp
3,920 ft	Ditch cuttings	—	Hordaland Gp
3,980 ft	Ditch cuttings	—	Hordaland Gp
4,070 ft	Ditch cuttings	—	Hordaland Gp
4,110 ft	Ditch cuttings	—	Hordaland Gp
4,170 ft	Ditch cuttings	—	Hordaland Gp
4,270 ft	Ditch cuttings	—	Hordaland Gp
4,290 ft	Ditch cuttings	—	Hordaland Gp
4,330 ft	Ditch cuttings	—	Hordaland Gp
4,370 ft	Ditch cuttings	—	Hordaland Gp
4,470 ft	Ditch cuttings	—	Hordaland Gp
4,490 ft	Ditch cuttings	—	Hordaland Gp

Seeing the material itself

The cores, cuttings, and thin sections listed here are physical samples held by the Norwegian Offshore Directorate in its Geobank, which has rooms for viewing and sampling them by booking. There are no images of thin sections or slides online; core photographs are the only pictures the Directorate publishes.

The Directorate's Geobank: viewing and sampling →

About this data

Norwegian Offshore Directorate (Sodir) FactPages, mirrored nightly and used under the Norwegian Licence for Open Government Data (NLOD). Depths are metres along the wellbore from the kelly bushing unless a row gives its own unit; older cores are filed in feet. A core's photographs are the ones whose titled interval overlaps the core's. Reports are placed beside the material they are about by their document type and file name, which is all the Directorate publishes about them. The unit beside a core, sample, test, or slide is the one whose top and base, in this wellbore's own tops, contain that depth; core and test depths are driller's depths, so an interval at a boundary can sit a few metres off. A zero the Directorate files for an unmeasured pressure, density, or temperature is shown as a dash. Availability is the Directorate's flag, not a stock check. Core photographs are links to its own files; Petrora does not hold copies.

Developers: this page as JSON is GET /v1/data/norway/wells/366, documented in the API reference.