NORWAY · WELLBORES · NPDID 170

11/10-1

Exploration · Wildcat · P&A · Dry · Syracuse Oils Norge A/S · PL 021

6 documents: reports, logs, and plots →

What was run in 11/10-1 and how the hole was built: the logs with their intervals, the casing strings with leak-off tests, and the mud at depth.

Logs you can open: composite and completion logs on file

The table below says which logs were run and over what interval. The curves themselves are held in Diskos, Norway's national data repository; its public portal lists what has been released for a wellbore and can be ordered for an administrative fee. Diskos public portal →

Logs

LogTop, mBase, mComposite log for the well
GR CAL SONICGR gamma ray · CAL caliper · SONIC sonic852,426On file: open →
VELOCITYVELOCITY velocity (check-shot) survey852,430On file: open →
IELIEL induction electrical log2542,429On file: open →

Casing and leak-off tests

CasingDiameter, inDepth, mHole, inHole depth, mLOT/FIT, g/cm³Test
Surf.cond.20130261310LOT
Interm.13 3/825317 1/22550LOT
Interm.9 5/81,02312 1/41,0250LOT
Open hole—2,4308 1/22,4300LOT

Drilling mud

5 READINGS · BY DEPTH

Depth, mWeight, g/cm³Viscosity, mPa·sYield point, PaType
2531.0500water based
1,0391.134015water based
1,4631.23406water based
1,8891.26438water based
2,4291.26405water based

The words under each tool string are Petrora's reading of the standard codes in it; a code we do not recognize is left as filed. The composite log is one file for the whole well. The Directorate does not say which runs or depths it draws on, so the link is the same on every row.

About this data

Norwegian Offshore Directorate (Sodir) FactPages, mirrored nightly and used under the Norwegian Licence for Open Government Data (NLOD). Log names are the Directorate's tool strings as filed; the plain-word readings beside them are Petrora's, from common industry abbreviations. Depths are metres along the wellbore from the kelly bushing; diameters are inches, as filed.

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