BIZTRAC BETA
Construction of railways and underground railways

LERØY VEDLIKEHOLD AS

Org. no. 816614112 Limited company (AS) Porsgrunn Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 478,000
Equity NOK 40,000
Incorporated 2016
Share capital NOK 30,000

LERØY VEDLIKEHOLD AS is registered as a limited company in Porsgrunn, Telemark with organisation number 816614112. The business is classified under construction of railways and underground railways (NACE 42.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie av personell for jernbane samt bygging og vedlikehold av jernbane.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 478,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 478,000
Equity
NOK 40,000
Est. value
NOK 1.3m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LERØY VEDLIKEHOLD AS?

LERØY INVEST AS
LERØY VEDLIKEHOLD AS
NOK 1.5m rev. · NOK 478,000 profit

LERØY VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LERØY VEDLIKEHOLD AS

Who owns LERØY VEDLIKEHOLD AS?

LERØY INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LERØY VEDLIKEHOLD AS?

LERØY VEDLIKEHOLD AS had revenue of NOK 1.5m in 2025.

Who is the general manager of LERØY VEDLIKEHOLD AS?

Svenn Roger Hjartsjø Lerøy is registered as general manager of LERØY VEDLIKEHOLD AS.

Where is LERØY VEDLIKEHOLD AS based?

LERØY VEDLIKEHOLD AS has its business address in Porsgrunn.

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.