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

LØYPE MASKINUTLEIE AS

Org. no. 932525224 Limited company (AS) Gausdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 15.0m
Operating profit NOK 2.0m
Equity NOK 31.7m
Incorporated 2023
Share capital NOK 118,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LØYPE MASKINUTLEIE AS is registered as a limited company in Gausdal, Innlandet with organisation number 932525224. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2023. Registered share capital is NOK 118,000, divided into 3000 shares. The company's stated purpose is: “Utleie av bygg- og anleggsmaskiner og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.0m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 15.0m
Operating profit
NOK 2.0m
Equity
NOK 31.7m
Est. value
NOK 22.9m

Financial health · 2024

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

Who owns LØYPE MASKINUTLEIE AS?

LØYPE AS
LØYPE MASKINUTLEIE AS
NOK 15.0m rev. · NOK 2.0m profit

LØYPE MASKINUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØYPE MASKINUTLEIE AS

Who owns LØYPE MASKINUTLEIE AS?

LØYPE AS is the largest registered owner, with 100.0%.

What is the revenue of LØYPE MASKINUTLEIE AS?

LØYPE MASKINUTLEIE AS had revenue of NOK 15.0m in 2024.

Where is LØYPE MASKINUTLEIE AS based?

LØYPE MASKINUTLEIE AS has its business address in Østre Gausdal.

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.