BIZTRAC BETA
Joinery installation

HIFU BYGG & EIENDOM AS

Org. no. 922172692 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 615,000
Equity NOK 581,000
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Nylig endring 2026-05-19 Adresseendring registrert 2026-05-19.

HIFU BYGG & EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 922172692. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Snekkerarbeid, kjøp, salg, utleie, utvikling og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 615,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 615,000
Equity
NOK 581,000
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns HIFU BYGG & EIENDOM AS?

LUIS FERNANDO HIDALGO LOPEZ
HIFU BYGG & EIENDOM AS
NOK 1.5m rev. · NOK 615,000 profit

HIFU BYGG & EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HIFU BYGG & EIENDOM AS

Who owns HIFU BYGG & EIENDOM AS?

LUIS FERNANDO HIDALGO LOPEZ is the largest registered owner, with 51.0%.

What is the revenue of HIFU BYGG & EIENDOM AS?

HIFU BYGG & EIENDOM AS had revenue of NOK 1.5m in 2024.

Who is the general manager of HIFU BYGG & EIENDOM AS?

Luis Fernando Hidalgo Lopez is registered as general manager of HIFU BYGG & EIENDOM AS.

Where is HIFU BYGG & EIENDOM AS based?

HIFU BYGG & EIENDOM AS has its business address in Gjettum.

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.