BIZTRAC BETA
COMPANY REGISTER PROFILE
936752950 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

JØLSTAD HOLDING AS

Org. no. 936752950 Limited company (AS) Asker Incorporated 2025 Active
Ownership graph ↗
Equity NOK 60.3m
Incorporated 2025
Share capital NOK 93,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-28.

JØLSTAD HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 936752950. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 93,000, divided into 9250 shares. The company's stated purpose is: “Holdingselskap for aksjer i Jølstad Eiendom AS og Jølstad Begravelsesbyrå AS.”.

Key figures · 2025

Equity
NOK 60.3m
Est. value
NOK 123.5m

Financial health · 2025

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

Who owns JØLSTAD HOLDING AS?

JØLSTAD HOLDING AS has 11 registered shareholders:

All shareholders and roles →

Which companies does JØLSTAD HOLDING AS own?

JØLSTAD HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JØLSTAD HOLDING AS

Who owns JØLSTAD HOLDING AS?

BAACO AS is the largest registered owner, with 20.1%.

Where is JØLSTAD HOLDING AS based?

JØLSTAD HOLDING AS has its business address in Billingstad.

Property

Business address Billingstadsletta 19B, 1396 Billingstad
Cadastral unit 3203-39/662/0/0

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