BIZTRAC BETA
Other real estate activities on a fee or contract basis

MELBY EIENDOM INVEST AS

Org. no. 918374701 Limited company (AS) Hamar Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 939,000
Operating profit NOK 393,000
Equity NOK 859,000
Incorporated 2016
Share capital NOK 100,000

MELBY EIENDOM INVEST AS is registered as a limited company in Hamar, Innlandet with organisation number 918374701. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering og forvaltning av fast eiendom og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 939,000 in revenue and NOK 393,000 in operating profit.

Key figures · 2025

Revenue
NOK 939,000
Operating profit
NOK 393,000
Equity
NOK 859,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns MELBY EIENDOM INVEST AS?

EINAR FRISLIE
MELBY EIENDOM INVEST AS
NOK 939,000 rev. · NOK 393,000 profit

MELBY EIENDOM INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MELBY EIENDOM INVEST AS own?

MELBY EIENDOM INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MELBY EIENDOM INVEST AS

Who owns MELBY EIENDOM INVEST AS?

EINAR FRISLIE is the largest registered owner, with 34.0%.

What is the revenue of MELBY EIENDOM INVEST AS?

MELBY EIENDOM INVEST AS had revenue of NOK 939,000 in 2025.

Where is MELBY EIENDOM INVEST AS based?

MELBY EIENDOM INVEST AS has its business address in Ridabu.

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.