BIZTRAC BETA
Rental and operating of own or leased real estate

MEL HEIA 33 AS

Org. no. 930681261 Limited company (AS) Lørenskog Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 40,000
Operating profit NOK −54,000
Equity NOK −32,000
Incorporated 2022
Share capital NOK 69,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−32k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).

MEL HEIA 33 AS is registered as a limited company in Lørenskog, Akershus with organisation number 930681261. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 69,000, divided into 100 shares. The company's stated purpose is: “Drift eller utleie av egen fast eiendom og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 40,000 in revenue and NOK −54,000 in operating profit.

Key figures · 2024

Revenue
NOK 40,000
Operating profit
NOK −54,000
Equity
NOK −32,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MEL HEIA 33 AS?

NORHOLM1 AS
MEL HEIA 33 AS
NOK 40,000 rev. · NOK −54,000 profit

MEL HEIA 33 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MEL HEIA 33 AS er morselskap for 1 datterselskap:

Frequently asked questions about MEL HEIA 33 AS

Who owns MEL HEIA 33 AS?

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

What is the revenue of MEL HEIA 33 AS?

MEL HEIA 33 AS had revenue of NOK 40,000 in 2024.

Where is MEL HEIA 33 AS based?

MEL HEIA 33 AS has its business address in Lørenskog.

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.