BIZTRAC BETA
Rental and operating of own or leased real estate

MØLLENDALSBAKKEN 6 AS

Org. no. 991238026 Limited company (AS) Bergen Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 335,000
Operating profit NOK −1.1m
Equity NOK 33.7m
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MØLLENDALSBAKKEN 6 AS is registered as a limited company in Bergen, Vestland with organisation number 991238026. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, drift og salg av fast eiendom og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 335,000 in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 335,000
Operating profit
NOK −1.1m
Equity
NOK 33.7m
Est. value
NOK 23.6m

Financial health · 2024

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

Who owns MØLLENDALSBAKKEN 6 AS?

VICO EIENDOM AS
MØLLENDALSBAKKEN 6 AS
NOK 335,000 rev. · NOK −1.1m profit

MØLLENDALSBAKKEN 6 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MØLLENDALSBAKKEN 6 AS

Who owns MØLLENDALSBAKKEN 6 AS?

VICO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of MØLLENDALSBAKKEN 6 AS?

MØLLENDALSBAKKEN 6 AS had revenue of NOK 335,000 in 2024.

Where is MØLLENDALSBAKKEN 6 AS based?

MØLLENDALSBAKKEN 6 AS has its business address in Bergen.

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.