BIZTRAC BETA
Development of building projects

MELBY PROSJEKT AS

Org. no. 926287052 Limited company (AS) Verdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −164,000
Equity NOK 757,000
Incorporated 2020
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−164k kr).

MELBY PROSJEKT AS is registered as a limited company in Verdal, Trøndelag with organisation number 926287052. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Utvikling og salg av egen fast eiendom ellers.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −164,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −164,000
Equity
NOK 757,000
Est. value
NOK 691,000

Financial health · 2024

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

Who owns MELBY PROSJEKT AS?

ARVE EDGAR MELBY
MELBY PROSJEKT AS
NOK 0 rev. · NOK −164,000 profit

MELBY PROSJEKT AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MELBY PROSJEKT AS own?

MELBY PROSJEKT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MELBY PROSJEKT AS

Who owns MELBY PROSJEKT AS?

ARVE EDGAR MELBY is the largest registered owner, with 33.3%.

What is the revenue of MELBY PROSJEKT AS?

MELBY PROSJEKT AS had revenue of NOK 0 in 2024.

Who is the general manager of MELBY PROSJEKT AS?

Thomas Melby is registered as general manager of MELBY PROSJEKT AS.

Where is MELBY PROSJEKT AS based?

MELBY PROSJEKT AS has its business address in Verdal.

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.