biztrac. BETA
COMPANY REGISTER PROFILE
978678769 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Drilling services for petroleum and natural gas extraction

LANGE RIGGPART AS

Org. no. 978678769 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Operating profit NOK −127,000
Equity NOK −36.5m
Incorporated 1997
Share capital NOK 470,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−36,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−127k kr).

LANGE RIGGPART AS is registered as a limited company in Oslo, Oslo with organisation number 978678769. The business is classified under drilling services for petroleum and natural gas extraction (NACE 09.101). The company was incorporated in 1997. Registered share capital is NOK 470,000, divided into 4700 shares. The company's stated purpose is: “Delta som komandittist i komandittselskapene Scan Pride L.P. og Scan Energy L.P., herunder salg og kjøp av andeler, samt å delta i andre selskaper samt å yte lån til og stille garantier overfor slike selskaper.”.

Key figures · 2025

Operating profit
NOK −127,000
▲ +19 %
Equity
NOK −36.5m
▲ +5 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
988.3%
Very good
Return on total assets
Solidity
-3650915700.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LANGE RIGGPART AS?

LANGE RIGGPART AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LANGE RIGGPART AS

Who owns LANGE RIGGPART AS?

Anniken Lange is the largest registered owner, with 40.0%.

Who is the general manager of LANGE RIGGPART AS?

Einar Christen Lange is registered as general manager of LANGE RIGGPART AS.

Where is LANGE RIGGPART AS based?

LANGE RIGGPART AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.