BIZTRAC BETA
Restaurant activities

IMA TURSENTER AS

Org. no. 813035782 Limited company (AS) Storfjord Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 401,000
Operating profit NOK 9,000
Equity NOK 31,000
Incorporated 2014
Share capital NOK 30,000

IMA TURSENTER AS is registered as a limited company in Storfjord, Troms with organisation number 813035782. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Servering av mat og drikke, utleie av hytter samt arrangementer med aktiviteter og velværetiltak. Samt omsetning av tur- og friluftsrelaterte produkter og det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 401,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 401,000
Operating profit
NOK 9,000
Equity
NOK 31,000
Est. value
NOK 56,000

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.0%
Weak
Equity as a share of total capital

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

Who owns IMA TURSENTER AS?

IMA HOLDING AS
IMA TURSENTER AS
NOK 401,000 rev. · NOK 9,000 profit

IMA TURSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IMA TURSENTER AS

Who owns IMA TURSENTER AS?

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

What is the revenue of IMA TURSENTER AS?

IMA TURSENTER AS had revenue of NOK 401,000 in 2025.

Who is the general manager of IMA TURSENTER AS?

Rolf Ole Steinvik is registered as general manager of IMA TURSENTER AS.

Where is IMA TURSENTER AS based?

IMA TURSENTER AS has its business address in Oteren.

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.