BIZTRAC BETA
Rental and operating of own or leased real estate

MELBY INVEST AS

Org. no. 939053956 Limited company (AS) Hustadvika Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 1.1m
Equity NOK 4.0m
Incorporated 1985
Share capital NOK 1.8m

MELBY INVEST AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 939053956. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1985. Registered share capital is NOK 1.8m, divided into 1825 shares. The company's stated purpose is: “Forretningsvirksomhet, samt det som naturlig står i forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 1.1m
Equity
NOK 4.0m
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.0%
Good
Equity as a share of total capital

Who owns MELBY INVEST AS?

BJØRN MELBY
MELBY INVEST AS
NOK 2.0m rev. · NOK 1.1m profit

MELBY INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MELBY INVEST AS own?

MELBY INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MELBY INVEST AS

Who owns MELBY INVEST AS?

BJØRN MELBY is the largest registered owner, with 91.0%.

What is the revenue of MELBY INVEST AS?

MELBY INVEST AS had revenue of NOK 2.0m in 2025.

Who is the general manager of MELBY INVEST AS?

Bjørn Melby is registered as general manager of MELBY INVEST AS.

Where is MELBY INVEST AS based?

MELBY INVEST AS has its business address in Eide.

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.