BIZTRAC BETA
Rental and operating of own or leased real estate

MEL TROMSØ 10 AS

Org. no. 932297299 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 242,000
Operating profit NOK 201,000
Equity NOK 168,000
Incorporated 2023
Share capital NOK 39,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MEL TROMSØ 10 AS is registered as a limited company in Tromsø, Troms with organisation number 932297299. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 39,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 242,000 in revenue and NOK 201,000 in operating profit.

Key figures · 2024

Revenue
NOK 242,000
Operating profit
NOK 201,000
Equity
NOK 168,000
Est. value
NOK 514,000

Financial health · 2024

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

Who owns MEL TROMSØ 10 AS?

ROG AS
MEL TROMSØ 10 AS
NOK 242,000 rev. · NOK 201,000 profit

MEL TROMSØ 10 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEL TROMSØ 10 AS

Who owns MEL TROMSØ 10 AS?

ROG AS is the largest registered owner, with 100.0%.

What is the revenue of MEL TROMSØ 10 AS?

MEL TROMSØ 10 AS had revenue of NOK 242,000 in 2024.

Who is the general manager of MEL TROMSØ 10 AS?

Roy Ove Gabrielsen is registered as general manager of MEL TROMSØ 10 AS.

Where is MEL TROMSØ 10 AS based?

MEL TROMSØ 10 AS has its business address in Kvaløya.

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.