BIZTRAC BETA
Site preparation

LOMEN MASKIN OG TRANSPORT AS

Org. no. 913356179 Limited company (AS) Vestre Slidre Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 144,000
Equity NOK 267,000
Incorporated 2014
Share capital NOK 30,000

LOMEN MASKIN OG TRANSPORT AS is registered as a limited company in Vestre Slidre, Innlandet with organisation number 913356179. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Graving, transport, og annet maskinarbeide, samt andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 144,000
Equity
NOK 267,000
Est. value
NOK 529,000

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.8%
Satisfactory
Equity as a share of total capital

Who owns LOMEN MASKIN OG TRANSPORT AS?

GJERMUND HAUGEN
LOMEN MASKIN OG TRANSPORT AS
NOK 2.8m rev. · NOK 144,000 profit

LOMEN MASKIN OG TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOMEN MASKIN OG TRANSPORT AS

Who owns LOMEN MASKIN OG TRANSPORT AS?

GJERMUND HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of LOMEN MASKIN OG TRANSPORT AS?

LOMEN MASKIN OG TRANSPORT AS had revenue of NOK 2.8m in 2025.

Who is the general manager of LOMEN MASKIN OG TRANSPORT AS?

Gjermund Haugen is registered as general manager of LOMEN MASKIN OG TRANSPORT AS.

Where is LOMEN MASKIN OG TRANSPORT AS based?

LOMEN MASKIN OG TRANSPORT AS has its business address in Lomen.

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.