BIZTRAC BETA
Other support activities for petroleum and natural gas extraction

FEARNLEY NORGE AS

Org. no. 986548742 Limited company (AS) Sandnes Incorporated 2004 Active
Ownership graph ↗
Operating profit NOK −93,000
Equity NOK −1.3m
Incorporated 2004
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−93k kr).

FEARNLEY NORGE AS is registered as a limited company in Sandnes, Rogaland with organisation number 986548742. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Brønnservice-tjenester, konsulenttjenester, kvalitetssikring og kvalitetskontroll, opplæring, ingeniør- og designtjenester knyttet til petroleumsindustrien, og hermed tilhørende virksomhet.”.

Key figures · 2025

Operating profit
NOK −93,000
Equity
NOK −1.3m

Financial health · 2025

Liquidity
0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-84.8%
Weak
Equity as a share of total capital

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

Who owns FEARNLEY NORGE AS?

FEARNLEY PROCTER GROUP LIMITED
FEARNLEY NORGE AS
· NOK −93,000 profit

FEARNLEY NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FEARNLEY NORGE AS

Who owns FEARNLEY NORGE AS?

FEARNLEY PROCTER GROUP LIMITED is the largest registered owner, with 100.0%.

Who is the general manager of FEARNLEY NORGE AS?

Kevin Allan Fearnley is registered as general manager of FEARNLEY NORGE AS.

Where is FEARNLEY NORGE AS based?

FEARNLEY NORGE AS has its business address in Sandnes.

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

Report a problem

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