BIZTRAC BETA
Sports activities n.e.c.

OLE HENRY AS

Org. no. 926775774 Limited company (AS) Larvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 605,000
Operating profit NOK 168,000
Equity NOK 131,000
Incorporated 2021
Share capital NOK 30,000

OLE HENRY AS is registered as a limited company in Larvik, Vestfold with organisation number 926775774. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av bilsport-team, drift av bilsport-events og markedsføringsarbeid, herunder annonsesalg og sponsortjenester, idrettsutøvelse og andre produkter/ tjenester som naturlig hører sammen med dette. Selskapet kan delta i andre selskaper med lignende virksomhet, samt kjøp og salg av aksjer i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 605,000 in revenue and NOK 168,000 in operating profit.

Key figures · 2025

Revenue
NOK 605,000
Operating profit
NOK 168,000
Equity
NOK 131,000
Est. value
NOK 612,000

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.2%
Good
Equity as a share of total capital

Who owns OLE HENRY AS?

OLE HENRY STEINSHOLT
OLE HENRY AS
NOK 605,000 rev. · NOK 168,000 profit

OLE HENRY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLE HENRY AS

Who owns OLE HENRY AS?

OLE HENRY STEINSHOLT is the largest registered owner, with 100.0%.

What is the revenue of OLE HENRY AS?

OLE HENRY AS had revenue of NOK 605,000 in 2025.

Who is the general manager of OLE HENRY AS?

Hedda Elisabeth Assev is registered as general manager of OLE HENRY AS.

Where is OLE HENRY AS based?

OLE HENRY AS has its business address in Kvelde.

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.