BIZTRAC BETA
Other captive investment companies

K.R. HOLDING AS

Org. no. 899257162 Limited company (AS) Modum Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK 6.8m
Incorporated 2012
Share capital NOK 75,000

Signals

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

K.R. HOLDING AS is registered as a limited company in Modum, Buskerud with organisation number 899257162. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 75,000, divided into 7500 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder å investere i aksjer, obligasjoner, fast eiendom, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 6.8m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns K.R. HOLDING AS?

KYRRE ROSENLUND
K.R. HOLDING AS
NOK 0 rev. · NOK −23,000 profit

K.R. HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does K.R. HOLDING AS own?

K.R. HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about K.R. HOLDING AS

Who owns K.R. HOLDING AS?

KYRRE ROSENLUND is the largest registered owner, with 100.0%.

What is the revenue of K.R. HOLDING AS?

K.R. HOLDING AS had revenue of NOK 0 in 2024.

Where is K.R. HOLDING AS based?

K.R. HOLDING AS has its business address in Åmot.

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.