BIZTRAC BETA
Development of building projects

FOKUS BYGG EIENDOM AS

Org. no. 991341951 Limited company (AS) Giske Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK −454,000
Equity NOK 2.9m
Incorporated 2007
Share capital NOK 750,000

Signals

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

FOKUS BYGG EIENDOM AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 991341951. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 750,000, divided into 750 shares. The company's stated purpose is: “Kjøp, oppføring, utvikling og salg av fast eiendom samt å eie, forvalte og leie ut boliger.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.8m in revenue and NOK −454,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK −454,000
Equity
NOK 2.9m
Est. value
NOK 13.4m

Financial health · 2024

Liquidity
2.62
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.3%
Satisfactory
Equity as a share of total capital

Who owns FOKUS BYGG EIENDOM AS?

FOKUSGRUPPEN AS
FOKUS BYGG EIENDOM AS
NOK 8.8m rev. · NOK −454,000 profit

FOKUS BYGG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOKUS BYGG EIENDOM AS

Who owns FOKUS BYGG EIENDOM AS?

FOKUSGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of FOKUS BYGG EIENDOM AS?

FOKUS BYGG EIENDOM AS had revenue of NOK 8.8m in 2024.

Who is the general manager of FOKUS BYGG EIENDOM AS?

Nils-Kristian Høyvik is registered as general manager of FOKUS BYGG EIENDOM AS.

Where is FOKUS BYGG EIENDOM AS based?

FOKUS BYGG EIENDOM AS has its business address in Valderøya.

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.