BIZTRAC BETA
Intermediation service activities for non-specialised retail sale

IVO AS

Org. no. 867382992 Limited company (AS) Alstahaug Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 48,000
Equity NOK 62,000
Incorporated 1993
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

IVO AS is registered as a limited company in Alstahaug, Nordland with organisation number 867382992. The business is classified under intermediation service activities for non-specialised retail sale (NACE 47.910). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kioskdrift og skipshandel og hva som står i forbindelse med dette. Herunder å delta i andre forretninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 48,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 48,000
Equity
NOK 62,000
Est. value
NOK 151,000

Financial health · 2024

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

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

Who owns IVO AS?

SEALINE PRODUCTS AS
IVO AS
NOK 1.5m rev. · NOK 48,000 profit

IVO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IVO AS

Who owns IVO AS?

SEALINE PRODUCTS AS is the largest registered owner, with 100.0%.

What is the revenue of IVO AS?

IVO AS had revenue of NOK 1.5m in 2024.

Who is the general manager of IVO AS?

Tommy Hesjevik is registered as general manager of IVO AS.

Where is IVO AS based?

IVO AS has its business address in Sandnessjøen.

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.