BIZTRAC BETA
Roofing activities

FANA BLIKK EIENDOM AS

Org. no. 933086003 Limited company (AS) Bergen Incorporated 1982 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK 3.7m
Equity NOK 6.0m
Incorporated 1982
Share capital NOK 78,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FANA BLIKK EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 933086003. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 1982. Registered share capital is NOK 78,000, divided into 50 shares. The company's stated purpose is: “Drift og utleie av fast eiendom samt å interessere seg i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK 3.7m
Equity
NOK 6.0m
Est. value
NOK 11.3m

Financial health · 2024

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.7%
Good
Equity as a share of total capital

Who owns FANA BLIKK EIENDOM AS?

FANA BLIKK GRUPPEN AS
FANA BLIKK EIENDOM AS
NOK 6.0m rev. · NOK 3.7m profit

FANA BLIKK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FANA BLIKK EIENDOM AS own?

FANA BLIKK EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FANA BLIKK EIENDOM AS

Who owns FANA BLIKK EIENDOM AS?

FANA BLIKK GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of FANA BLIKK EIENDOM AS?

FANA BLIKK EIENDOM AS had revenue of NOK 6.0m in 2024.

Where is FANA BLIKK EIENDOM AS based?

FANA BLIKK EIENDOM AS has its business address in Nesttun.

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.