BIZTRAC BETA
Freight transport by road

ALPINSERVICE KRAN OG TRANSPORT AS

Org. no. 930699993 Limited company (AS) Vestnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 238,000
Equity NOK 500,000
Incorporated 2022
Share capital NOK 100,000

ALPINSERVICE KRAN OG TRANSPORT AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 930699993. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tjenester innen kran og transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 238,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 238,000
Equity
NOK 500,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns ALPINSERVICE KRAN OG TRANSPORT AS?

ALPINSERVICE HOLDING AS
ALPINSERVICE KRAN OG TRANSPORT AS
NOK 1.2m rev. · NOK 238,000 profit

ALPINSERVICE KRAN OG TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ALPINSERVICE KRAN OG TRANSPORT AS

Who owns ALPINSERVICE KRAN OG TRANSPORT AS?

ALPINSERVICE HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of ALPINSERVICE KRAN OG TRANSPORT AS?

ALPINSERVICE KRAN OG TRANSPORT AS had revenue of NOK 1.2m in 2025.

Who is the general manager of ALPINSERVICE KRAN OG TRANSPORT AS?

Håvard Lid is registered as general manager of ALPINSERVICE KRAN OG TRANSPORT AS.

Where is ALPINSERVICE KRAN OG TRANSPORT AS based?

ALPINSERVICE KRAN OG TRANSPORT AS has its business address in Vestnes.

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.