BIZTRAC BETA
COMPANY REGISTER PROFILE
929000676 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Retail sale of sports equipment

ISOTWO AS

Org. no. 929000676 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 1,000
Incorporated 2022
Share capital NOK 30,000

ISOTWO AS is registered as a limited company in Stavanger, Rogaland with organisation number 929000676. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Utvikling og salg av produkter innen trening og rehabilitering.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 1,000
Est. value
NOK 2,000

Financial health · 2025

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

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

Who owns ISOTWO AS?

ISOTWO AS
· NOK 0 profit

ISOTWO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ISOTWO AS er morselskap for 2 datterselskaper:

Frequently asked questions about ISOTWO AS

Who owns ISOTWO AS?

CELL INVEST AS is the largest registered owner, with 100.0%.

Where is ISOTWO AS based?

ISOTWO AS has its business address in Stavanger.

Property

Business address Lervigbrygga 128, 4014 Stavanger
Cadastral unit 1103-54/1076/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 81 units

36 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.