BIZTRAC BETA
Industrial product and fashion design activities

MARITIME GUARDIAN AS

Org. no. 932768569 Limited company (AS) Vågan Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 191,000
Operating profit NOK −152,000
Equity NOK −128,000
Incorporated 2024
Share capital NOK 35,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−128k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−152k kr).

MARITIME GUARDIAN AS is registered as a limited company in Vågan, Nordland with organisation number 932768569. 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 35,000, divided into 35000 shares. The company's stated purpose is: “Utvikle autonome sikkerhetssystemer til båter.”. The most recent filed accounts, for the 2024 financial year, show NOK 191,000 in revenue and NOK −152,000 in operating profit.

Key figures · 2024

Revenue
NOK 191,000
Operating profit
NOK −152,000
Equity
NOK −128,000

Financial health · 2024

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

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

Who owns MARITIME GUARDIAN AS?

NORTH SIEK HOLDING AS
MARITIME GUARDIAN AS
NOK 191,000 rev. · NOK −152,000 profit

MARITIME GUARDIAN AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about MARITIME GUARDIAN AS

Who owns MARITIME GUARDIAN AS?

NORTH SIEK HOLDING AS is the largest registered owner, with 68.6%.

What is the revenue of MARITIME GUARDIAN AS?

MARITIME GUARDIAN AS had revenue of NOK 191,000 in 2024.

Where is MARITIME GUARDIAN AS based?

MARITIME GUARDIAN AS has its business address in Laupstad.

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.