biztrac. BETA
COMPANY REGISTER PROFILE
929565371 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ARSK-HOLDING AS

Org. no. 929565371 Limited company (AS) Bergen Incorporated 2022 Active
Operating profit NOK −4,000
Equity NOK 15,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

ARSK-HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 929565371. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −4,000
▲ +8 %
Equity
NOK 15,000
▼ −19 %
Est. value
NOK 18,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
3.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ARSK-HOLDING AS?

ARSK-HOLDING AS
· NOK −4,000 profit

ARSK-HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARSK-HOLDING AS own?

ARSK-HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARSK-HOLDING AS

Who owns ARSK-HOLDING AS?

Arvid Skulstad is the largest registered owner, with 100.0%.

Who is the general manager of ARSK-HOLDING AS?

Stian Skulstad is registered as general manager of ARSK-HOLDING AS.

Where is ARSK-HOLDING AS based?

ARSK-HOLDING AS has its business address in Nesttun.

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.