biztrac. BETA
COMPANY REGISTER PROFILE
822709362 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

ORNELL LEYSER AS

Org. no. 822709362 Limited company (AS) Larvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 557,000
Operating profit NOK 461,000
Equity NOK 634,000
Incorporated 2019
Share capital NOK 30,000

ORNELL LEYSER AS is registered as a limited company in Larvik, Vestfold with organisation number 822709362. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Produksjon og salg av skreddersydde klær samt andre tjenester og produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 557,000 in revenue and NOK 461,000 in operating profit.

Key figures · 2025

Revenue
NOK 557,000
▲ +53 %
Operating profit
NOK 461,000
▲ +72 %
Equity
NOK 634,000
▲ +195 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
7.31
Very good
Current assets ÷ current liabilities
Profitability
89.5%
Very good
Return on total assets
Solidity
86.2%
Very good
Equity as a share of total capital

Who owns ORNELL LEYSER AS?

ORNELL LEYSER AS
NOK 557,000 rev. · NOK 461,000 profit

ORNELL LEYSER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ORNELL LEYSER AS

Who owns ORNELL LEYSER AS?

Thomas Løge Ornell is the largest registered owner, with 80.0%.

What is the revenue of ORNELL LEYSER AS?

ORNELL LEYSER AS had revenue of NOK 557,000 in 2025.

Who is the general manager of ORNELL LEYSER AS?

Thomas Løge Ornell is registered as general manager of ORNELL LEYSER AS.

Where is ORNELL LEYSER AS based?

ORNELL LEYSER AS has its business address in Larvik.

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.