BIZTRAC BETA
Site preparation

GJERLØW MASKIN OG TRANSPORT AS

Org. no. 917198772 Limited company (AS) Sogndal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 9.0m
Operating profit NOK 446,000
Equity NOK 2.9m
Incorporated 2016
Share capital NOK 705,000

GJERLØW MASKIN OG TRANSPORT AS is registered as a limited company in Sogndal, Vestland with organisation number 917198772. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2016. Registered share capital is NOK 705,000, divided into 705 shares. The company's stated purpose is: “Entreprenørtenester, samt det som naturlig står i forbindelse med dette. Kjøpt og salg av eigedom, utleige av eigedom.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.0m in revenue and NOK 446,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.0m
Operating profit
NOK 446,000
Equity
NOK 2.9m
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.8%
Good
Equity as a share of total capital

Who owns GJERLØW MASKIN OG TRANSPORT AS?

MAGNE GJERLØW
GJERLØW MASKIN OG TRANSPORT AS
NOK 9.0m rev. · NOK 446,000 profit

GJERLØW MASKIN OG TRANSPORT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GJERLØW MASKIN OG TRANSPORT AS

Who owns GJERLØW MASKIN OG TRANSPORT AS?

MAGNE GJERLØW is the largest registered owner, with 33.3%.

What is the revenue of GJERLØW MASKIN OG TRANSPORT AS?

GJERLØW MASKIN OG TRANSPORT AS had revenue of NOK 9.0m in 2025.

Who is the general manager of GJERLØW MASKIN OG TRANSPORT AS?

Øyvind Gjerløw is registered as general manager of GJERLØW MASKIN OG TRANSPORT AS.

Where is GJERLØW MASKIN OG TRANSPORT AS based?

GJERLØW MASKIN OG TRANSPORT AS has its business address in Leikanger.

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.