BIZTRAC BETA
Rental and operating of own or leased real estate

MELHUS EIENDOM AS

Org. no. 919627050 Limited company (AS) Melhus Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 2.3m
Equity NOK 16.9m
Incorporated 2017
Share capital NOK 92,000

Signals

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

MELHUS EIENDOM AS is registered as a limited company in Melhus, Trøndelag with organisation number 919627050. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 92,000, divided into 30600 shares. The company's stated purpose is: “Kjøp-, salg-, utleie- og drift av eiendommer og hva som dermed står i forbindelse samt deltakelse i andre firmaer som aksjonær.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 2.3m
Equity
NOK 16.9m
Est. value
NOK 17.5m

Financial health · 2024

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

Who owns MELHUS EIENDOM AS?

KNAUSEBU HOLDING AS
MELHUS EIENDOM AS
NOK 3.5m rev. · NOK 2.3m profit

MELHUS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MELHUS EIENDOM AS own?

MELHUS EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MELHUS EIENDOM AS

Who owns MELHUS EIENDOM AS?

KNAUSEBU HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MELHUS EIENDOM AS?

MELHUS EIENDOM AS had revenue of NOK 3.5m in 2024.

Where is MELHUS EIENDOM AS based?

MELHUS EIENDOM AS has its business address in Melhus.

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.