BIZTRAC BETA
Other captive investment companies

KROGSVEEN HJEM AS

Org. no. 933995690 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 2.7m
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KROGSVEEN HJEM AS is registered as a limited company in Bærum, Akershus with organisation number 933995690. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3486 shares. The company's stated purpose is: “Å drive investeringsvirksomhet i selskaper, herunder aksjer og andre verdipapirer, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 2.7m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns KROGSVEEN HJEM AS?

EIENDOMSMEGLER KROGSVEEN AS
KROGSVEEN HJEM AS
NOK 0 rev. · NOK 0 profit

KROGSVEEN HJEM AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does KROGSVEEN HJEM AS own?

KROGSVEEN HJEM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KROGSVEEN HJEM AS

Who owns KROGSVEEN HJEM AS?

EIENDOMSMEGLER KROGSVEEN AS is the largest registered owner, with 52.4%.

What is the revenue of KROGSVEEN HJEM AS?

KROGSVEEN HJEM AS had revenue of NOK 0 in 2024.

Where is KROGSVEEN HJEM AS based?

KROGSVEEN HJEM AS has its business address in Fornebu.

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.