BIZTRAC BETA
Business and other management consultancy activities

ITN COBO ADVISORS AS

Org. no. 934471385 Limited company (AS) Os Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −202
Equity NOK 30,000
Incorporated 2024
Share capital NOK 36,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−202 kr).

ITN COBO ADVISORS AS is registered as a limited company in Os, Innlandet with organisation number 934471385. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 36,000, divided into 30000 shares. The company's stated purpose is: “Rådgivingsselskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −202 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −202
Equity
NOK 30,000
Est. value
NOK 49,000

Financial health · 2024

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 ITN COBO ADVISORS AS?

LARS ULVERUD
ITN COBO ADVISORS AS
NOK 0 rev. · NOK −202 profit

ITN COBO ADVISORS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ITN COBO ADVISORS AS own?

ITN COBO ADVISORS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ITN COBO ADVISORS AS

Who owns ITN COBO ADVISORS AS?

LARS ULVERUD is the largest registered owner, with 50.0%.

What is the revenue of ITN COBO ADVISORS AS?

ITN COBO ADVISORS AS had revenue of NOK 0 in 2024.

Where is ITN COBO ADVISORS AS based?

ITN COBO ADVISORS AS has its business address in Os I Østerdalen.

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.