BIZTRAC BETA
Computer programming activities

IO SAGA AS

Org. no. 928725219 Limited company (AS) Bodø Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 75
Equity NOK −131,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−131k kr).

IO SAGA AS is registered as a limited company in Bodø, Nordland with organisation number 928725219. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Import og salg av kontorrekvisita igjennom nettbutikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 75 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 75
Equity
NOK −131,000
Est. value
NOK 326

Financial health · 2024

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

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

Who owns IO SAGA AS?

JØRN OTTO SOLDEVILLA HANSEN
IO SAGA AS
NOK 0 rev. · NOK 75 profit

IO SAGA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IO SAGA AS own?

IO SAGA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about IO SAGA AS

Who owns IO SAGA AS?

JØRN OTTO SOLDEVILLA HANSEN is the largest registered owner, with 100.0%.

What is the revenue of IO SAGA AS?

IO SAGA AS had revenue of NOK 0 in 2024.

Who is the general manager of IO SAGA AS?

Jørn Otto Soldevilla Hansen is registered as general manager of IO SAGA AS.

Where is IO SAGA AS based?

IO SAGA AS has its business address in Misvær.

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.