BIZTRAC BETA
Development of building projects

HA-MJ AS

Org. no. 916366701 Limited company (AS) Voss Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.2m
Equity NOK 7.4m
Incorporated 2015
Share capital NOK 500,000

Signals

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

HA-MJ AS is registered as a limited company in Voss, Vestland with organisation number 916366701. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Investering i eigendom og anna som naturlig hører saman med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.2m
Equity
NOK 7.4m
Est. value
NOK 7.1m

Financial health · 2024

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

Who owns HA-MJ AS?

OPAL INVEST AS
HA-MJ AS
NOK 2.2m rev. · NOK 1.2m profit

HA-MJ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HA-MJ AS own?

HA-MJ AS holds a stake in 1 company:

See the full ownership structure →

Group structure

HA-MJ AS er morselskap for 1 datterselskap:

Frequently asked questions about HA-MJ AS

Who owns HA-MJ AS?

OPAL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HA-MJ AS?

HA-MJ AS had revenue of NOK 2.2m in 2025.

Who is the general manager of HA-MJ AS?

Alf Opheim is registered as general manager of HA-MJ AS.

Where is HA-MJ AS based?

HA-MJ AS has its business address in Voss.

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.