BIZTRAC BETA
Business and other management consultancy activities

ULMAR AS

Org. no. 979970609 Limited company (AS) Ulstein Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK −57,000
Equity NOK 94.0m
Incorporated 1998
Share capital NOK 162,000

Signals

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

ULMAR AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 979970609. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1998. Registered share capital is NOK 162,000, divided into 81001 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, aksjer og andre verdipapirer, samt utføre konsulenttjenester innenfor definerte områder.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK −57,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK −57,000
Equity
NOK 94.0m
Est. value
NOK 56.5m

Financial health · 2024

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

Who owns ULMAR AS?

STIG ULSTEIN
ULMAR AS
NOK 2.3m rev. · NOK −57,000 profit

ULMAR AS has 6 registered shareholders:

All shareholders and roles →

Which companies does ULMAR AS own?

ULMAR AS holds stakes in 13 companies:

See the full ownership structure →

Frequently asked questions about ULMAR AS

Who owns ULMAR AS?

STIG ULSTEIN is the largest registered owner, with 32.7%.

What is the revenue of ULMAR AS?

ULMAR AS had revenue of NOK 2.3m in 2024.

Who is the general manager of ULMAR AS?

Stig Ulstein is registered as general manager of ULMAR AS.

Where is ULMAR AS based?

ULMAR 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.