BIZTRAC BETA
Business and other management consultancy activities

ISB CO-ACTIVE AS

Org. no. 998613469 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −104,000
Equity NOK 337,000
Incorporated 2012
Share capital NOK 40,000

Signals

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

ISB CO-ACTIVE AS is registered as a limited company in Bergen, Vestland with organisation number 998613469. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Lederutvikling og coaching, salgs og presentasjonstrening, teambygging samt forretningsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −104,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −104,000
Equity
NOK 337,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.54
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.4%
Good
Equity as a share of total capital

Who owns ISB CO-ACTIVE AS?

INA KRISTINE SCHJØTT BRACKMAN
ISB CO-ACTIVE AS
NOK 1.0m rev. · NOK −104,000 profit

ISB CO-ACTIVE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ISB CO-ACTIVE AS

Who owns ISB CO-ACTIVE AS?

INA KRISTINE SCHJØTT BRACKMAN is the largest registered owner, with 100.0%.

What is the revenue of ISB CO-ACTIVE AS?

ISB CO-ACTIVE AS had revenue of NOK 1.0m in 2025.

Who is the general manager of ISB CO-ACTIVE AS?

Ina Kristine Schjøtt Brackman is registered as general manager of ISB CO-ACTIVE AS.

Where is ISB CO-ACTIVE AS based?

ISB CO-ACTIVE AS has its business address in Paradis.

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.