BIZTRAC BETA
Industrial product and fashion design activities

URO SUBSEA PRODUCTS AS

Org. no. 933546454 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

URO SUBSEA PRODUCTS AS is registered as a limited company in Bergen, Vestland with organisation number 933546454. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikle produkter for bruk Subsea.”.

Key figures · 2025

Operating profit
NOK −9,000
Equity
NOK 15,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns URO SUBSEA PRODUCTS AS?

UXEN AS
URO SUBSEA PRODUCTS AS
· NOK −9,000 profit

URO SUBSEA PRODUCTS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does URO SUBSEA PRODUCTS AS own?

URO SUBSEA PRODUCTS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about URO SUBSEA PRODUCTS AS

Who owns URO SUBSEA PRODUCTS AS?

UXEN AS is the largest registered owner, with 60.0%.

Who is the general manager of URO SUBSEA PRODUCTS AS?

Fredrik Normann Hansen is registered as general manager of URO SUBSEA PRODUCTS AS.

Where is URO SUBSEA PRODUCTS AS based?

URO SUBSEA PRODUCTS AS has its business address in Bergen.

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.