biztrac. BETA
COMPANY REGISTER PROFILE
919423420 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

BASIV HOLDING AS

Org. no. 919423420 Limited company (AS) Trondheim Incorporated 2017 Active
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 353,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

BASIV HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 919423420. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eierskap av andre selskaper og eiendom. Kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
▲ +21 %
Equity
NOK 353,000
▲ +167 %
Est. value
NOK 986,000

Financial health · 2025

Liquidity
85.56
Very good
Current assets ÷ current liabilities
Profitability
96.9%
Very good
Return on total assets
Solidity
86.3%
Very good
Equity as a share of total capital

Who owns BASIV HOLDING AS?

BASIV HOLDING AS
NOK 0 rev. · NOK −4,000 profit

BASIV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BASIV HOLDING AS own?

BASIV HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BASIV HOLDING AS

Who owns BASIV HOLDING AS?

Bjørn-Arne Sivertsen is the largest registered owner, with 100.0%.

What is the revenue of BASIV HOLDING AS?

BASIV HOLDING AS had revenue of NOK 0 in 2025.

Where is BASIV HOLDING AS based?

BASIV HOLDING AS has its business address in Charlottenlund.

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

Report a problem

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