BIZTRAC BETA
Business and other management consultancy activities

U-TURN VENTURES AS

Org. no. 983436927 Limited company (AS) Nesodden Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 11,000
Operating profit NOK −164,000
Equity NOK 35.0m
Incorporated 2001
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−164k kr).

U-TURN VENTURES AS is registered as a limited company in Nesodden, Akershus with organisation number 983436927. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2001. Registered share capital is NOK 200,000, divided into 100000 shares. The company's stated purpose is: “Investeringsvirksomhet og generell rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 11,000 in revenue and NOK −164,000 in operating profit.

Key figures · 2024

Revenue
NOK 11,000
Operating profit
NOK −164,000
Equity
NOK 35.0m
Est. value
NOK 38.8m

Financial health · 2024

Liquidity
14.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
93.5%
Very good
Equity as a share of total capital

Who owns U-TURN VENTURES AS?

LARS TORE BRANDEGGEN
U-TURN VENTURES AS
NOK 11,000 rev. · NOK −164,000 profit

U-TURN VENTURES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does U-TURN VENTURES AS own?

U-TURN VENTURES AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about U-TURN VENTURES AS

Who owns U-TURN VENTURES AS?

LARS TORE BRANDEGGEN is the largest registered owner, with 100.0%.

What is the revenue of U-TURN VENTURES AS?

U-TURN VENTURES AS had revenue of NOK 11,000 in 2024.

Where is U-TURN VENTURES AS based?

U-TURN VENTURES AS has its business address in Nesoddtangen.

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.