BIZTRAC BETA
Uoppgitt

BARO SOLUTIONS AS

Org. no. 834491192 Limited company (AS) Ulstein Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 407,000
Incorporated 2024
Share capital NOK 120,000

Signals

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

BARO SOLUTIONS AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 834491192. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 120,000, divided into 120000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, inkludert, men ikke begrenset til, kjøp, salg og forvaltning av aksjer, obligasjoner, derivater og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 407,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns BARO SOLUTIONS AS?

ULMATEC EIENDOM AS
BARO SOLUTIONS AS
NOK 0 rev. · NOK −12,000 profit

BARO SOLUTIONS AS has 9 registered shareholders:

All shareholders and roles →

Which companies does BARO SOLUTIONS AS own?

BARO SOLUTIONS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BARO SOLUTIONS AS

Who owns BARO SOLUTIONS AS?

ULMATEC EIENDOM AS is the largest registered owner, with 42.0%.

What is the revenue of BARO SOLUTIONS AS?

BARO SOLUTIONS AS had revenue of NOK 0 in 2025.

Where is BARO SOLUTIONS AS based?

BARO SOLUTIONS AS has its business address in Ulsteinvik.

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.