BIZTRAC BETA
Restaurant activities

M BYHAVEN AS

Org. no. 997875915 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK −569,000
Equity NOK −602,000
Incorporated 2012
Employees 15
Share capital NOK 43,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−602k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−569k kr).

M BYHAVEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 997875915. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 15 registered employees. Registered share capital is NOK 43,000, divided into 42857 shares. The company's stated purpose is: “Drift av restaurant samt alt som hermed hører med.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK −569,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK −569,000
Equity
NOK −602,000

Financial health · 2025

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

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

Who owns M BYHAVEN AS?

REMY HOLDING AS
M BYHAVEN AS
NOK 5.1m rev. · NOK −569,000 profit

M BYHAVEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M BYHAVEN AS

Who owns M BYHAVEN AS?

REMY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of M BYHAVEN AS?

M BYHAVEN AS had revenue of NOK 5.1m in 2025.

Who is the general manager of M BYHAVEN AS?

Remy-Andre Nordvik is registered as general manager of M BYHAVEN AS.

Where is M BYHAVEN AS based?

M BYHAVEN AS has its business address in Trondheim.

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.