BIZTRAC BETA
Other captive investment companies

KAPITTEL 11 AS

Org. no. 919316322 Limited company (AS) Bjørnafjorden Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 500,000
Operating profit NOK −161,000
Equity NOK 419,000
Incorporated 2017
Share capital NOK 285,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−161k kr).

KAPITTEL 11 AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 919316322. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 285,000, divided into 950 shares. The company's stated purpose is: “Investeringer i alle typer finansielle instrumenter, samt drive virksomhet som står i naturlig tilknytning til dette, herunder ha eierandeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 500,000 in revenue and NOK −161,000 in operating profit.

Key figures · 2025

Revenue
NOK 500,000
Operating profit
NOK −161,000
Equity
NOK 419,000
Est. value
NOK 679,000

Financial health · 2025

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.3%
Very good
Equity as a share of total capital

Who owns KAPITTEL 11 AS?

ERLEND SOLBERG
KAPITTEL 11 AS
NOK 500,000 rev. · NOK −161,000 profit

KAPITTEL 11 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAPITTEL 11 AS own?

KAPITTEL 11 AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KAPITTEL 11 AS

Who owns KAPITTEL 11 AS?

ERLEND SOLBERG is the largest registered owner, with 100.0%.

What is the revenue of KAPITTEL 11 AS?

KAPITTEL 11 AS had revenue of NOK 500,000 in 2025.

Where is KAPITTEL 11 AS based?

KAPITTEL 11 AS has its business address in Os.

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.