BIZTRAC BETA
Other captive investment companies

FREDHEIM 1450 INVEST AS

Org. no. 913256093 Limited company (AS) Nesodden Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 600,000
Operating profit NOK −439,000
Equity NOK 49.7m
Incorporated 2013
Share capital NOK 30,000

Signals

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

FREDHEIM 1450 INVEST AS is registered as a limited company in Nesodden, Akershus with organisation number 913256093. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer og konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 600,000 in revenue and NOK −439,000 in operating profit.

Key figures · 2025

Revenue
NOK 600,000
Operating profit
NOK −439,000
Equity
NOK 49.7m
Est. value
NOK 34.4m

Financial health · 2025

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

Who owns FREDHEIM 1450 INVEST AS?

KINE HANSEN KROGSTAD
FREDHEIM 1450 INVEST AS
NOK 600,000 rev. · NOK −439,000 profit

FREDHEIM 1450 INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FREDHEIM 1450 INVEST AS own?

FREDHEIM 1450 INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FREDHEIM 1450 INVEST AS

Who owns FREDHEIM 1450 INVEST AS?

KINE HANSEN KROGSTAD is the largest registered owner, with 33.3%.

What is the revenue of FREDHEIM 1450 INVEST AS?

FREDHEIM 1450 INVEST AS had revenue of NOK 600,000 in 2025.

Where is FREDHEIM 1450 INVEST AS based?

FREDHEIM 1450 INVEST AS has its business address in Nesoddtangen.

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.