BIZTRAC BETA
Other captive investment companies

KBR INVEST AS

Org. no. 896322532 Limited company (AS) Stavanger Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 17,000
Operating profit NOK −4,000
Equity NOK 407,000
Incorporated 2010
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KBR INVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 896322532. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 17,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 17,000
Operating profit
NOK −4,000
Equity
NOK 407,000
Est. value
NOK 361,000

Financial health · 2025

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

Who owns KBR INVEST AS?

KRISTOFFER BRÆKKE
KBR INVEST AS
NOK 17,000 rev. · NOK −4,000 profit

KBR INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KBR INVEST AS own?

KBR INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about KBR INVEST AS

Who owns KBR INVEST AS?

KRISTOFFER BRÆKKE is the largest registered owner, with 100.0%.

What is the revenue of KBR INVEST AS?

KBR INVEST AS had revenue of NOK 17,000 in 2025.

Where is KBR INVEST AS based?

KBR INVEST 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.