BIZTRAC BETA
Business and other management consultancy activities

UTVIKLINGSPARTNER UPAS AS

Org. no. 899031032 Limited company (AS) Nes Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK −1.3m
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

UTVIKLINGSPARTNER UPAS AS is registered as a limited company in Nes, Akershus with organisation number 899031032. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med bedriftsrådgivning og utvikling av bedrifter.”.

Key figures · 2025

Operating profit
NOK −17,000
Equity
NOK −1.3m

Financial health · 2025

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

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

Who owns UTVIKLINGSPARTNER UPAS AS?

JAN IVAR SØRENSEN
UTVIKLINGSPARTNER UPAS AS
· NOK −17,000 profit

UTVIKLINGSPARTNER UPAS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does UTVIKLINGSPARTNER UPAS AS own?

UTVIKLINGSPARTNER UPAS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about UTVIKLINGSPARTNER UPAS AS

Who owns UTVIKLINGSPARTNER UPAS AS?

JAN IVAR SØRENSEN is the largest registered owner, with 50.0%.

Who is the general manager of UTVIKLINGSPARTNER UPAS AS?

Ivar Gaute Strøm is registered as general manager of UTVIKLINGSPARTNER UPAS AS.

Where is UTVIKLINGSPARTNER UPAS AS based?

UTVIKLINGSPARTNER UPAS AS has its business address in Vormsund.

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.