BIZTRAC BETA
Rental and operating of own or leased real estate

MEGLERHUSET RELE HOLDING AS

Org. no. 924332506 Limited company (AS) Haugesund Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −138,000
Equity NOK 7.5m
Incorporated 2019
Share capital NOK 501,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−138k kr).

MEGLERHUSET RELE HOLDING AS is registered as a limited company in Haugesund, Rogaland with organisation number 924332506. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 501,000, divided into 501000 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −138,000
Equity
NOK 7.5m
Est. value
NOK 45.5m

Financial health · 2025

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

Who owns MEGLERHUSET RELE HOLDING AS?

SKUDENES & AAKRA SPAREBANK
MEGLERHUSET RELE HOLDING AS
· NOK −138,000 profit

MEGLERHUSET RELE HOLDING AS has 7 registered shareholders:

All shareholders and roles →

Which companies does MEGLERHUSET RELE HOLDING AS own?

MEGLERHUSET RELE HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about MEGLERHUSET RELE HOLDING AS

Who owns MEGLERHUSET RELE HOLDING AS?

SKUDENES & AAKRA SPAREBANK is the largest registered owner, with 34.0%.

Who is the general manager of MEGLERHUSET RELE HOLDING AS?

Marius Kallevik is registered as general manager of MEGLERHUSET RELE HOLDING AS.

Where is MEGLERHUSET RELE HOLDING AS based?

MEGLERHUSET RELE HOLDING AS has its business address in Haugesund.

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.