BIZTRAC BETA
Uoppgitt

FLIK EIENDOM AS

Org. no. 823169442 Limited company (AS) Stryn Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 491,000
Equity NOK −808,000
Incorporated 2019
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−808k kr).

FLIK EIENDOM AS is registered as a limited company in Stryn, Vestland with organisation number 823169442. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Utleie av egen eller leid fast eiendom ellers.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 491,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 491,000
Equity
NOK −808,000
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
4.05
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FLIK EIENDOM AS?

JOHAN OLAV PARR FLO
FLIK EIENDOM AS
NOK 2.4m rev. · NOK 491,000 profit

FLIK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLIK EIENDOM AS own?

FLIK EIENDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about FLIK EIENDOM AS

Who owns FLIK EIENDOM AS?

JOHAN OLAV PARR FLO is the largest registered owner, with 100.0%.

What is the revenue of FLIK EIENDOM AS?

FLIK EIENDOM AS had revenue of NOK 2.4m in 2024.

Who is the general manager of FLIK EIENDOM AS?

Johan Olav Parr Flo is registered as general manager of FLIK EIENDOM AS.

Where is FLIK EIENDOM AS based?

FLIK EIENDOM AS has its business address in Stryn.

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.