BIZTRAC BETA
Uoppgitt

LRN TRANSPORT HOLDING AS

Org. no. 935610974 Limited company (AS) Vestre Toten Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 100,000
Operating profit NOK 56,000
Equity NOK 4.4m
Incorporated 2025
Share capital NOK 4.3m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

LRN TRANSPORT HOLDING AS is registered as a limited company in Vestre Toten, Innlandet with organisation number 935610974. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 4.3m, divided into 400 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper.”.

Key figures

Revenue
NOK 100,000
Operating profit
NOK 56,000
Equity
NOK 4.4m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns LRN TRANSPORT HOLDING AS?

MARTIN HOLDING AS
LRN TRANSPORT HOLDING AS
NOK 100,000 rev. · NOK 56,000 profit

LRN TRANSPORT HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LRN TRANSPORT HOLDING AS own?

LRN TRANSPORT HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

LRN TRANSPORT HOLDING AS er morselskap for 4 datterselskaper:

Frequently asked questions about LRN TRANSPORT HOLDING AS

Who owns LRN TRANSPORT HOLDING AS?

MARTIN HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of LRN TRANSPORT HOLDING AS?

LRN TRANSPORT HOLDING AS had revenue of NOK 100,000.

Where is LRN TRANSPORT HOLDING AS based?

LRN TRANSPORT HOLDING AS has its business address in Raufoss.

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.