BIZTRAC BETA
COMPANY REGISTER PROFILE
994457217 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

CASCO AS

Org. no. 994457217 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 1.6m
Incorporated 2009
Share capital NOK 100,000

Signals

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

CASCO AS is registered as a limited company in Bergen, Vestland with organisation number 994457217. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i finans- og realaktiva.”.

Key figures · 2025

Operating profit
NOK −1,000
▲ +0 %
Equity
NOK 1.6m
▼ −0 %
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns CASCO AS?

CASCO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CASCO AS own?

CASCO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CASCO AS

Who owns CASCO AS?

CATO SKULSTAD is the largest registered owner, with 70.0%.

Where is CASCO AS based?

CASCO AS has its business address in Arnatveit.

Property

Business address Arnatveitvegen 137, 5262 Arnatveit
Cadastral unit 4601-287/217/0/0

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