BIZTRAC BETA
Legal activities

ADVOKATENE LEIROS & OLSEN AS

Org. no. 989080822 Limited company (AS) Tromsø Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 15.7m
Operating profit NOK 1.4m
Equity NOK 4.9m
Incorporated 2005
Employees 14
Share capital NOK 200,000

ADVOKATENE LEIROS & OLSEN AS is registered as a limited company in Tromsø, Troms with organisation number 989080822. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2005 and has 14 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drive advokatvirksomhet, samt hva som naturlig og lovlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.7m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 15.7m
Operating profit
NOK 1.4m
Equity
NOK 4.9m
Est. value
NOK 9.7m

Financial health · 2025

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

Who owns ADVOKATENE LEIROS & OLSEN AS?

TORE LEIROS
ADVOKATENE LEIROS & OLSEN AS
NOK 15.7m rev. · NOK 1.4m profit

ADVOKATENE LEIROS & OLSEN AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATENE LEIROS & OLSEN AS

Who owns ADVOKATENE LEIROS & OLSEN AS?

TORE LEIROS is the largest registered owner, with 16.0%.

What is the revenue of ADVOKATENE LEIROS & OLSEN AS?

ADVOKATENE LEIROS & OLSEN AS had revenue of NOK 15.7m in 2025.

Who is the general manager of ADVOKATENE LEIROS & OLSEN AS?

Tore Leiros is registered as general manager of ADVOKATENE LEIROS & OLSEN AS.

Where is ADVOKATENE LEIROS & OLSEN AS based?

ADVOKATENE LEIROS & OLSEN AS has its business address in Tromsø.

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.