biztrac. BETA
COMPANY REGISTER PROFILE
915184014 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

LEIRANGER MASKIN AS

Org. no. 915184014 Limited company (AS) Tysvær Incorporated 2015 Active
Revenue 2025 NOK 329,000
Operating profit NOK 75,000
Equity NOK 1.0m
Incorporated 2015
Share capital NOK 30,000

LEIRANGER MASKIN AS is registered as a limited company in Tysvær, Rogaland with organisation number 915184014. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Entreprenørtjenester innen landbruk, graving, riving og transport og hva som herved står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 329,000 in revenue and NOK 75,000 in operating profit.

Former names: RYFYLKE LEKTER AS

Key figures · 2025

Revenue
NOK 329,000
▲ +43 %
Operating profit
NOK 75,000
▲ +164 %
Equity
NOK 1.0m
▲ +8 %
Est. value
NOK 731,000

Financial health · 2025

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

Who owns LEIRANGER MASKIN AS?

LEIRANGER MASKIN AS
NOK 329,000 rev. · NOK 75,000 profit

LEIRANGER MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEIRANGER MASKIN AS

Who owns LEIRANGER MASKIN AS?

Oddbjørn Jensen is the largest registered owner, with 100.0%.

What is the revenue of LEIRANGER MASKIN AS?

LEIRANGER MASKIN AS had revenue of NOK 329,000 in 2025.

Who is the general manager of LEIRANGER MASKIN AS?

Oddbjørn Jensen is registered as general manager of LEIRANGER MASKIN AS.

Where is LEIRANGER MASKIN AS based?

LEIRANGER MASKIN AS has its business address in Nedstrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.