BIZTRAC BETA
Other captive investment companies

BLÅNOTER AS

Org. no. 892108102 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −42,000
Equity NOK 5.1m
Incorporated 2007
Share capital NOK 100,000

Signals

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

BLÅNOTER AS is registered as a limited company in Stavanger, Rogaland with organisation number 892108102. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1855804 shares. The company's stated purpose is: “Investering i verdipapirer, herunder deltakelse i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −42,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −42,000
Equity
NOK 5.1m
Est. value
NOK 4.7m

Financial health · 2024

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.1%
Very good
Equity as a share of total capital

Who owns BLÅNOTER AS?

SVEIN OLAV KERSBERGEN
BLÅNOTER AS
NOK 0 rev. · NOK −42,000 profit

BLÅNOTER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLÅNOTER AS own?

BLÅNOTER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLÅNOTER AS

Who owns BLÅNOTER AS?

SVEIN OLAV KERSBERGEN is the largest registered owner, with 100.0%.

What is the revenue of BLÅNOTER AS?

BLÅNOTER AS had revenue of NOK 0 in 2024.

Who is the general manager of BLÅNOTER AS?

Øystein Lunde Ohna is registered as general manager of BLÅNOTER AS.

Where is BLÅNOTER AS based?

BLÅNOTER AS has its business address in Stavanger.

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.