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

MYKLES UTLEIGE AS

Org. no. 926432370 Limited company (AS) Herøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −351,000
Equity NOK −20,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−20k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−351k kr).

MYKLES UTLEIGE AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 926432370. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 40 shares. The company's stated purpose is: “Kjøp, salg og utleie av maskinutstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −351,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −351,000
Equity
NOK −20,000

Financial health · 2024

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.6%
Weak
Equity as a share of total capital

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

Who owns MYKLES UTLEIGE AS?

No shareholders are registered for MYKLES UTLEIGE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MYKLES UTLEIGE AS

What is the revenue of MYKLES UTLEIGE AS?

MYKLES UTLEIGE AS had revenue of NOK 1.9m in 2024.

Who is the general manager of MYKLES UTLEIGE AS?

Sindre Evjen Myklebust is registered as general manager of MYKLES UTLEIGE AS.

Where is MYKLES UTLEIGE AS based?

MYKLES UTLEIGE AS has its business address in Nerlandsøy.

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.