BIZTRAC BETA
Computer programming activities

TIV HOLDING AS

Org. no. 916775520 Limited company (AS) Karmøy Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 131,000
Equity NOK 884,000
Incorporated 2016
Share capital NOK 60,000

TIV HOLDING AS is registered as a limited company in Karmøy, Rogaland with organisation number 916775520. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Drive med investeringer og nyetableringer, inkludert kjøp og salg av aksjer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 131,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 131,000
Equity
NOK 884,000
Est. value
NOK 827,000

Financial health · 2024

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.2%
Good
Equity as a share of total capital

Who owns TIV HOLDING AS?

TOR IVAR ROSSEBØ VÅGE
TIV HOLDING AS
NOK 2.1m rev. · NOK 131,000 profit

TIV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIV HOLDING AS own?

TIV HOLDING AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about TIV HOLDING AS

Who owns TIV HOLDING AS?

TOR IVAR ROSSEBØ VÅGE is the largest registered owner, with 100.0%.

What is the revenue of TIV HOLDING AS?

TIV HOLDING AS had revenue of NOK 2.1m in 2024.

Who is the general manager of TIV HOLDING AS?

Tor Ivar Rossebø Våge is registered as general manager of TIV HOLDING AS.

Where is TIV HOLDING AS based?

TIV HOLDING AS has its business address in Karmsund.

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.