BIZTRAC BETA
Rental and operating of own or leased real estate

MELLOMVIKA 35 AS

Org. no. 998879892 Limited company (AS) Rana Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 6.7m
Operating profit NOK 5.5m
Equity NOK 3.2m
Incorporated 2012
Share capital NOK 42,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-22 Adresseendring registrert 2026-06-22.

MELLOMVIKA 35 AS is registered as a limited company in Rana, Nordland with organisation number 998879892. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 42,000, divided into 42 shares. The company's stated purpose is: “Å eie og leie ut fast eiendom, m.v.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.7m in revenue and NOK 5.5m in operating profit.

Key figures · 2024

Revenue
NOK 6.7m
Operating profit
NOK 5.5m
Equity
NOK 3.2m
Est. value
NOK 10.7m

Financial health · 2024

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

Who owns MELLOMVIKA 35 AS?

RANA NÆRINGSPARK AS
MELLOMVIKA 35 AS
NOK 6.7m rev. · NOK 5.5m profit

MELLOMVIKA 35 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MELLOMVIKA 35 AS

Who owns MELLOMVIKA 35 AS?

RANA NÆRINGSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of MELLOMVIKA 35 AS?

MELLOMVIKA 35 AS had revenue of NOK 6.7m in 2024.

Who is the general manager of MELLOMVIKA 35 AS?

Hans Johnny Høgås is registered as general manager of MELLOMVIKA 35 AS.

Where is MELLOMVIKA 35 AS based?

MELLOMVIKA 35 AS has its business address in Mo I Rana.

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.