BIZTRAC BETA
COMPANY REGISTER PROFILE
919971703 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

KASO HOLDING AS

Org. no. 919971703 Limited company (AS) Stjørdal Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −39,000
Equity NOK 5.5m
Incorporated 2017
Share capital NOK 31,000

Signals

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

KASO HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 919971703. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 31,000, divided into 8790 shares. The company's stated purpose is: “Å investere og eie aksjer i andre selskap, samt alt som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −39,000
▲ +41 %
Equity
NOK 5.5m
▼ −5 %
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
83.3%
Very good
Equity as a share of total capital

Who owns KASO HOLDING AS?

KASO HOLDING AS
· NOK −39,000 profit

KASO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KASO HOLDING AS

Who owns KASO HOLDING AS?

KARI SOFIE MYRVOLD is the largest registered owner, with 100.0%.

Where is KASO HOLDING AS based?

KASO HOLDING AS has its business address in Stjørdal.

Property

Business address Sutterøygata 14, 7502 Stjørdal
Cadastral unit 5035-82/75/0/0

11 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.