BIZTRAC BETA
Rental and operating of own or leased real estate

MEL VESTBY 11 AS

Org. no. 930716103 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 150,000
Operating profit NOK −14,000
Equity NOK −33,000
Incorporated 2022
Share capital NOK 74,000

Signals

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

MEL VESTBY 11 AS is registered as a limited company in Tromsø, Troms with organisation number 930716103. 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 74,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 150,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 150,000
Operating profit
NOK −14,000
Equity
NOK −33,000

Financial health · 2024

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.4%
Weak
Equity as a share of total capital

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

Who owns MEL VESTBY 11 AS?

GML HOLDING AS
MEL VESTBY 11 AS
NOK 150,000 rev. · NOK −14,000 profit

MEL VESTBY 11 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MEL VESTBY 11 AS er morselskap for 2 datterselskaper:

Frequently asked questions about MEL VESTBY 11 AS

Who owns MEL VESTBY 11 AS?

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

What is the revenue of MEL VESTBY 11 AS?

MEL VESTBY 11 AS had revenue of NOK 150,000 in 2024.

Where is MEL VESTBY 11 AS based?

MEL VESTBY 11 AS has its business address in Tromsdalen.

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.