BIZTRAC BETA
Business and other management consultancy activities

FEARNLEY ADVISORS AS

Org. no. 998788153 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 21.1m
Operating profit NOK −105,000
Equity NOK 88,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−105k kr).

FEARNLEY ADVISORS AS is registered as a limited company in Oslo, Oslo with organisation number 998788153. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 15000 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.1m in revenue and NOK −105,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.1m
Operating profit
NOK −105,000
Equity
NOK 88,000
Est. value
NOK 1.7bn

Financial health · 2024

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

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

Who owns FEARNLEY ADVISORS AS?

GLAAMENE INDUSTRIER AS
FEARNLEY ADVISORS AS
NOK 21.1m rev. · NOK −105,000 profit

FEARNLEY ADVISORS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FEARNLEY ADVISORS AS

Who owns FEARNLEY ADVISORS AS?

GLAAMENE INDUSTRIER AS is the largest registered owner, with 33.3%.

What is the revenue of FEARNLEY ADVISORS AS?

FEARNLEY ADVISORS AS had revenue of NOK 21.1m in 2024.

Where is FEARNLEY ADVISORS AS based?

FEARNLEY ADVISORS 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 15.06.2026.

Report a problem

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