BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

LRK MASKIN AS

Org. no. 933198391 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 780,000
Equity NOK 600,000
Incorporated 2024
Share capital NOK 30,000

LRK MASKIN AS is registered as a limited company in Oslo, Oslo with organisation number 933198391. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av anleggsmaskiner og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 780,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 780,000
Equity
NOK 600,000
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns LRK MASKIN AS?

LEIF RUNE KROGH
LRK MASKIN AS
NOK 1.8m rev. · NOK 780,000 profit

LRK MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LRK MASKIN AS own?

LRK MASKIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LRK MASKIN AS

Who owns LRK MASKIN AS?

LEIF RUNE KROGH is the largest registered owner, with 100.0%.

What is the revenue of LRK MASKIN AS?

LRK MASKIN AS had revenue of NOK 1.8m in 2024.

Who is the general manager of LRK MASKIN AS?

Leif Rune Krogh is registered as general manager of LRK MASKIN AS.

Where is LRK MASKIN AS based?

LRK MASKIN AS has its business address in Oslo.

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.