BIZTRAC BETA
Other technical consultancy

UCON OFFSHORE AS

Org. no. 976764765 Limited company (AS) Bærum Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 262,000
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

UCON OFFSHORE AS is registered as a limited company in Bærum, Akershus with organisation number 976764765. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Konsulentvirksomhet primært mot offshoresektoren både innenlands og internasjonalt. Videre skal selskapet kunne foreta og være aktiv i forvaltning av ulike investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 262,000
Est. value
NOK 426,000

Financial health · 2025

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

Who owns UCON OFFSHORE AS?

JAN BØRGE USLAND
UCON OFFSHORE AS
NOK 0 rev. · NOK −13,000 profit

UCON OFFSHORE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UCON OFFSHORE AS

Who owns UCON OFFSHORE AS?

JAN BØRGE USLAND is the largest registered owner, with 100.0%.

What is the revenue of UCON OFFSHORE AS?

UCON OFFSHORE AS had revenue of NOK 0 in 2025.

Who is the general manager of UCON OFFSHORE AS?

Jan Børge Usland is registered as general manager of UCON OFFSHORE AS.

Where is UCON OFFSHORE AS based?

UCON OFFSHORE AS has its business address in Snarøya.

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.