BIZTRAC BETA
Dental practice care activities

JBL HOLDING AS

Org. no. 991103856 Limited company (AS) Ringsaker Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 358,000
Equity NOK 4.8m
Incorporated 2007
Share capital NOK 100,000

JBL HOLDING AS is registered as a limited company in Ringsaker, Innlandet with organisation number 991103856. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tannlegevirksomhet og annen virksomhet som naturlig hører til dette området. Selskapet skal videre kunne eie og drive fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 358,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 358,000
Equity
NOK 4.8m
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns JBL HOLDING AS?

JØRN WILGRIM BANG-LARSEN
JBL HOLDING AS
NOK 1.4m rev. · NOK 358,000 profit

JBL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JBL HOLDING AS own?

JBL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JBL HOLDING AS

Who owns JBL HOLDING AS?

JØRN WILGRIM BANG-LARSEN is the largest registered owner, with 100.0%.

What is the revenue of JBL HOLDING AS?

JBL HOLDING AS had revenue of NOK 1.4m in 2024.

Who is the general manager of JBL HOLDING AS?

Jørn Wilgrim Bang-Larsen is registered as general manager of JBL HOLDING AS.

Where is JBL HOLDING AS based?

JBL HOLDING AS has its business address in Brumunddal.

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

Report a problem

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