BIZTRAC BETA
Rental and operating of own or leased real estate

MÆLABAKKEN AS

Org. no. 926096915 Limited company (AS) Melhus Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 100,000
Operating profit NOK −259,000
Equity NOK −2.1m
Incorporated 2020
Share capital NOK 42,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−259k kr).
  • Nylig endring 2026-07-16 Adresseendring registrert 2026-07-16.

MÆLABAKKEN AS is registered as a limited company in Melhus, Trøndelag with organisation number 926096915. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 42,000, divided into 100 shares. The company's stated purpose is: “Utleie, kjøp og salg av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 100,000 in revenue and NOK −259,000 in operating profit.

Key figures · 2025

Revenue
NOK 100,000
Operating profit
NOK −259,000
Equity
NOK −2.1m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-135.1%
Weak
Equity as a share of total capital

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

Who owns MÆLABAKKEN AS?

Ragnar Vigdal
MÆLABAKKEN AS
NOK 100,000 rev. · NOK −259,000 profit

MÆLABAKKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MÆLABAKKEN AS

Who owns MÆLABAKKEN AS?

Ragnar Vigdal is the largest registered owner, with 50.0%.

What is the revenue of MÆLABAKKEN AS?

MÆLABAKKEN AS had revenue of NOK 100,000 in 2025.

Where is MÆLABAKKEN AS based?

MÆLABAKKEN AS has its business address in Melhus.

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.