BIZTRAC BETA
Uoppgitt

HAMREMOEN HOLDING AS

Org. no. 927176874 Limited company (AS) Hadsel Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 262,000
Operating profit NOK −95,000
Equity NOK 253,000
Incorporated 2021
Share capital NOK 580,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−95k kr).
  • Nylig endring 2026-06-23 Aksjekapital registrert 2026-06-23.

HAMREMOEN HOLDING AS is registered as a limited company in Hadsel, Nordland with organisation number 927176874. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 580,000, divided into 10000 shares. The company's stated purpose is: “Investering i andre selskaper, samt investering og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 262,000 in revenue and NOK −95,000 in operating profit.

Key figures · 2025

Revenue
NOK 262,000
Operating profit
NOK −95,000
Equity
NOK 253,000
Est. value
NOK 297,000

Financial health · 2025

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

Who owns HAMREMOEN HOLDING AS?

ESPEN HAMREMOEN
HAMREMOEN HOLDING AS
NOK 262,000 rev. · NOK −95,000 profit

HAMREMOEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAMREMOEN HOLDING AS own?

HAMREMOEN HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about HAMREMOEN HOLDING AS

Who owns HAMREMOEN HOLDING AS?

ESPEN HAMREMOEN is the largest registered owner, with 100.0%.

What is the revenue of HAMREMOEN HOLDING AS?

HAMREMOEN HOLDING AS had revenue of NOK 262,000 in 2025.

Where is HAMREMOEN HOLDING AS based?

HAMREMOEN HOLDING AS has its business address in Stokmarknes.

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.