BIZTRAC BETA
Retail sale of medical and orthopaedic goods

HILLESTAD STOKKE AS

Org. no. 997311221 Limited company (AS) Bergen Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 20.1m
Operating profit NOK 1.5m
Equity NOK 390,000
Incorporated 2011
Employees 12
Share capital NOK 100,000

HILLESTAD STOKKE AS is registered as a limited company in Bergen, Vestland with organisation number 997311221. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2011 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive optiker virksomhet samt alt som står i forbindelse med dette. Selskapet kan også investere i andre selskap og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.1m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 20.1m
Operating profit
NOK 1.5m
Equity
NOK 390,000
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns HILLESTAD STOKKE AS?

LIV BEATE HILLESTAD
HILLESTAD STOKKE AS
NOK 20.1m rev. · NOK 1.5m profit

HILLESTAD STOKKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HILLESTAD STOKKE AS

Who owns HILLESTAD STOKKE AS?

LIV BEATE HILLESTAD is the largest registered owner, with 60.0%.

What is the revenue of HILLESTAD STOKKE AS?

HILLESTAD STOKKE AS had revenue of NOK 20.1m in 2025.

Who is the general manager of HILLESTAD STOKKE AS?

Henrike Cornelie Hennies-Samplawsky is registered as general manager of HILLESTAD STOKKE AS.

Where is HILLESTAD STOKKE AS based?

HILLESTAD STOKKE AS has its business address in Ulset.

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.