biztrac. BETA
COMPANY REGISTER PROFILE
833590162 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hotels and similar accommodation

MESNABAKKEN AS

Org. no. 833590162 Limited company (AS) Ringsaker Incorporated 2024 Active
Revenue 2025 NOK 1.2m
Operating profit NOK −424,000
Equity NOK −158,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−158k kr).

MESNABAKKEN AS is registered as a limited company in Ringsaker, Innlandet with organisation number 833590162. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Overnatting, selskaper, events og andre produkter/tjenester som naturlig hører sammen med dette. Herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −424,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +17 %
Operating profit
NOK −424,000
▼ −1712 %
Equity
NOK −158,000
▼ −159 %

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
-103.1%
Not satisfactory
Return on total assets
Solidity
-47.0%
Weak
Equity as a share of total capital

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

Who owns MESNABAKKEN AS?

MESNABAKKEN AS
NOK 1.2m rev. · NOK −424,000 profit

MESNABAKKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MESNABAKKEN AS

Who owns MESNABAKKEN AS?

MESNA HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of MESNABAKKEN AS?

MESNABAKKEN AS had revenue of NOK 1.2m in 2025.

Where is MESNABAKKEN AS based?

MESNABAKKEN AS has its business address in Mesnali.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.