BIZTRAC BETA
Rental and operating of own or leased real estate

FAMILIEFORETAGET INVEST AS

Org. no. 921220723 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 947,000
Operating profit NOK 415,000
Equity NOK 1.6m
Incorporated 2018
Share capital NOK 1.1m

FAMILIEFORETAGET INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 921220723. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 1.1m, divided into 11000 shares. The company's stated purpose is: “Å investere innen verdipapirer og fast eiendom og alt som hermed står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 947,000 in revenue and NOK 415,000 in operating profit.

Key figures · 2025

Revenue
NOK 947,000
Operating profit
NOK 415,000
Equity
NOK 1.6m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns FAMILIEFORETAGET INVEST AS?

MARIKEN KIELLAND BLOM
FAMILIEFORETAGET INVEST AS
NOK 947,000 rev. · NOK 415,000 profit

FAMILIEFORETAGET INVEST AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about FAMILIEFORETAGET INVEST AS

Who owns FAMILIEFORETAGET INVEST AS?

MARIKEN KIELLAND BLOM is the largest registered owner, with 20.0%.

What is the revenue of FAMILIEFORETAGET INVEST AS?

FAMILIEFORETAGET INVEST AS had revenue of NOK 947,000 in 2025.

Who is the general manager of FAMILIEFORETAGET INVEST AS?

Erlend Flaaen Ramnefjell is registered as general manager of FAMILIEFORETAGET INVEST AS.

Where is FAMILIEFORETAGET INVEST AS based?

FAMILIEFORETAGET INVEST AS has its business address in Oslo.

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.