BIZTRAC BETA
Legal activities

ADVOKATENE TORSTRUPLERUM AS

Org. no. 931777424 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 1.7m
Equity NOK 1.5m
Incorporated 2023
Share capital NOK 30,000

ADVOKATENE TORSTRUPLERUM AS is registered as a limited company in Stavanger, Rogaland with organisation number 931777424. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av advokattjenester, eie og investere i aksjer og andre selskaper og virksomheter, samt deltakelse av enhver art i andre forretningsforetagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 1.7m
Equity
NOK 1.5m
Est. value
NOK 6.5m

Financial health · 2025

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

Who owns ADVOKATENE TORSTRUPLERUM AS?

KNUT INGAR LERUM
ADVOKATENE TORSTRUPLERUM AS
NOK 5.6m rev. · NOK 1.7m profit

ADVOKATENE TORSTRUPLERUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATENE TORSTRUPLERUM AS

Who owns ADVOKATENE TORSTRUPLERUM AS?

KNUT INGAR LERUM is the largest registered owner, with 50.0%.

What is the revenue of ADVOKATENE TORSTRUPLERUM AS?

ADVOKATENE TORSTRUPLERUM AS had revenue of NOK 5.6m in 2025.

Who is the general manager of ADVOKATENE TORSTRUPLERUM AS?

Knut Ingar Lerum is registered as general manager of ADVOKATENE TORSTRUPLERUM AS.

Where is ADVOKATENE TORSTRUPLERUM AS based?

ADVOKATENE TORSTRUPLERUM AS has its business address in Stavanger.

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.