BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

ULLA MARITIME AS

Org. no. 916959389 Limited company (AS) Haram Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 9,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

ULLA MARITIME AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 916959389. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Produksjon og salg av utstyr og tjenester til maritim næring.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 9,000
Est. value
NOK 11,000

Financial health · 2025

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

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

Who owns ULLA MARITIME AS?

BJØRN NOGVA
ULLA MARITIME AS
NOK 0 rev. · NOK −3,000 profit

ULLA MARITIME AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ULLA MARITIME AS

Who owns ULLA MARITIME AS?

BJØRN NOGVA is the largest registered owner, with 51.0%.

What is the revenue of ULLA MARITIME AS?

ULLA MARITIME AS had revenue of NOK 0 in 2025.

Who is the general manager of ULLA MARITIME AS?

Bjørn Nogva is registered as general manager of ULLA MARITIME AS.

Where is ULLA MARITIME AS based?

ULLA MARITIME AS has its business address in Søvik.

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.