BIZTRAC BETA
Passenger transport by cableways and ski lifts

TURUTUNET AS

Org. no. 923118128 Limited company (AS) Flå Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK −4.1m
Equity NOK −13.6m
Incorporated 2019
Share capital NOK 6.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−13,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,1 mill kr).

TURUTUNET AS is registered as a limited company in Flå, Buskerud with organisation number 923118128. The business is classified under passenger transport by cableways and ski lifts (NACE 49.340). The company was incorporated in 2019. Registered share capital is NOK 6.0m, divided into 30 shares. The company's stated purpose is: “Investering og drift av skiheis og varmestue/kafè og andre arrangementer i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK −4.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK −4.1m
Equity
NOK −13.6m

Financial health · 2024

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

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

Who owns TURUTUNET AS?

TURUFJELL AS
TURUTUNET AS
NOK 3.1m rev. · NOK −4.1m profit

TURUTUNET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TURUTUNET AS

Who owns TURUTUNET AS?

TURUFJELL AS is the largest registered owner, with 100.0%.

What is the revenue of TURUTUNET AS?

TURUTUNET AS had revenue of NOK 3.1m in 2024.

Who is the general manager of TURUTUNET AS?

Martine Vee is registered as general manager of TURUTUNET AS.

Where is TURUTUNET AS based?

TURUTUNET AS has its business address in Flå.

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.