BIZTRAC BETA
Construction of residential and non-residential buildings

FLESJÅ HOLDING AS

Org. no. 998887461 Limited company (AS) Ålesund Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −29,000
Equity NOK 118,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

FLESJÅ HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 998887461. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 400 shares. The company's stated purpose is: “Holdingselskap, herunder å eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 118,000
Est. value
NOK 121,000

Financial health · 2024

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.5%
Not satisfactory
Equity as a share of total capital

Who owns FLESJÅ HOLDING AS?

No shareholders are registered for FLESJÅ HOLDING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does FLESJÅ HOLDING AS own?

FLESJÅ HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FLESJÅ HOLDING AS

What is the revenue of FLESJÅ HOLDING AS?

FLESJÅ HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of FLESJÅ HOLDING AS?

Kristian Emblem Flesjå is registered as general manager of FLESJÅ HOLDING AS.

Where is FLESJÅ HOLDING AS based?

FLESJÅ HOLDING AS has its business address in Ålesund.

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.