BIZTRAC BETA
Rental and operating of own or leased real estate

FLISA EIENDOMSINVEST AS

Org. no. 992136952 Limited company (AS) Kristiansand Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 88.7m
Incorporated 2007
Share capital NOK 2.2m

Signals

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

FLISA EIENDOMSINVEST AS is registered as a limited company in Kristiansand, Agder with organisation number 992136952. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 2.2m, divided into 2250 shares. The company's stated purpose is: “Å investere i eiendom, kjøp, salg og utleie av fast eiendom, samt investere i aksjer, fond og andre verdipapirer, samt hva hermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −23,000
Equity
NOK 88.7m
Est. value
NOK 109.3m

Financial health · 2024

Liquidity
0.22
Not satisfactory
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 FLISA EIENDOMSINVEST AS?

MICHEL INVEST AS
FLISA EIENDOMSINVEST AS
· NOK −23,000 profit

FLISA EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLISA EIENDOMSINVEST AS own?

FLISA EIENDOMSINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FLISA EIENDOMSINVEST AS

Who owns FLISA EIENDOMSINVEST AS?

MICHEL INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of FLISA EIENDOMSINVEST AS?

Johan Bernt Michelsen is registered as general manager of FLISA EIENDOMSINVEST AS.

Where is FLISA EIENDOMSINVEST AS based?

FLISA EIENDOMSINVEST AS has its business address in Kristiansand S.

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.