BIZTRAC BETA
Repair and maintenance of machinery

LONO MEKANISKE AS

Org. no. 824558442 Limited company (AS) Ullensvang Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 549,000
Equity NOK 1.9m
Incorporated 2020
Share capital NOK 30,000

LONO MEKANISKE AS is registered as a limited company in Ullensvang, Vestland with organisation number 824558442. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby og selge tjenester innen reparasjon og vedlikehald av maskinar og utstyr, samt utleie av arbeidskraft til andre oppdrag, og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 549,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 549,000
Equity
NOK 1.9m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns LONO MEKANISKE AS?

SVEN-ARILD LONO
LONO MEKANISKE AS
NOK 2.1m rev. · NOK 549,000 profit

LONO MEKANISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LONO MEKANISKE AS

Who owns LONO MEKANISKE AS?

SVEN-ARILD LONO is the largest registered owner, with 100.0%.

What is the revenue of LONO MEKANISKE AS?

LONO MEKANISKE AS had revenue of NOK 2.1m in 2025.

Where is LONO MEKANISKE AS based?

LONO MEKANISKE AS has its business address in Røldal.

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.