biztrac. BETA
COMPANY REGISTER PROFILE
920741657 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

M12 TROMSØ AS

Org. no. 920741657 Limited company (AS) Tromsø Incorporated 2018 Active
Revenue 2025 NOK 5.5m
Operating profit NOK −3.1m
Equity NOK 9.2m
Incorporated 2018
Employees 10
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3,1 mill kr).

M12 TROMSØ AS is registered as a limited company in Tromsø, Troms with organisation number 920741657. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Driv av bar og restaurant og hva som naturlig hører sammen med dette. Deltagelse i annen forretningsvirksomhet og hva som står i forbindelse hermed”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK −3.1m in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
▼ −48 %
Operating profit
NOK −3.1m
▼ −114 %
Equity
NOK 9.2m
▼ −3 %
Est. value
NOK 8.4m

Financial health · 2025

Liquidity
5.20
Very good
Current assets ÷ current liabilities
Profitability
-27.4%
Not satisfactory
Return on total assets
Solidity
90.5%
Very good
Equity as a share of total capital

Who owns M12 TROMSØ AS?

M12 TROMSØ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about M12 TROMSØ AS

Who owns M12 TROMSØ AS?

M12 MOR AS is the largest registered owner, with 91.0%.

What is the revenue of M12 TROMSØ AS?

M12 TROMSØ AS had revenue of NOK 5.5m in 2025.

Who is the general manager of M12 TROMSØ AS?

Karl-Henning Fahlstrøm Svendsen is registered as general manager of M12 TROMSØ AS.

Where is M12 TROMSØ AS based?

M12 TROMSØ AS has its business address in Tromsø.

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.