BIZTRAC BETA
Uoppgitt

AS OLE LEGRAN HOLDING

Org. no. 933105075 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 654,000
Operating profit NOK 314,000
Equity NOK 268,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-23 Adresseendring registrert 2026-04-23.

AS OLE LEGRAN HOLDING is registered as a limited company in Trondheim, Trøndelag with organisation number 933105075. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i selskaper og eiendom, aksjer og andre verdipapirer herunder lånefinansierte investeringer med verdipapier og valuta.”. The most recent filed accounts, for the 2025 financial year, show NOK 654,000 in revenue and NOK 314,000 in operating profit.

Key figures · 2025

Revenue
NOK 654,000
Operating profit
NOK 314,000
Equity
NOK 268,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns AS OLE LEGRAN HOLDING?

OLE ADRIAN LEGRAN
AS OLE LEGRAN HOLDING
NOK 654,000 rev. · NOK 314,000 profit

AS OLE LEGRAN HOLDING has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AS OLE LEGRAN HOLDING

Who owns AS OLE LEGRAN HOLDING?

OLE ADRIAN LEGRAN is the largest registered owner, with 100.0%.

What is the revenue of AS OLE LEGRAN HOLDING?

AS OLE LEGRAN HOLDING had revenue of NOK 654,000 in 2025.

Who is the general manager of AS OLE LEGRAN HOLDING?

Ole Adrian Legran is registered as general manager of AS OLE LEGRAN HOLDING.

Where is AS OLE LEGRAN HOLDING based?

AS OLE LEGRAN HOLDING has its business address in Heimdal.

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.