BIZTRAC BETA
Site preparation

NESBØ MASKIN OG TRANSPORT AS

Org. no. 915347649 Limited company (AS) Aurland Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 28,000
Equity NOK 945,000
Incorporated 2015
Share capital NOK 100,000

NESBØ MASKIN OG TRANSPORT AS is registered as a limited company in Aurland, Vestland with organisation number 915347649. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet, utleige av maskiner, følgebiltenester og anna som naturleg fell saman med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 28,000
Equity
NOK 945,000
Est. value
NOK 550,000

Financial health · 2025

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

Who owns NESBØ MASKIN OG TRANSPORT AS?

KAY MARTIN NESBØ
NESBØ MASKIN OG TRANSPORT AS
NOK 2.3m rev. · NOK 28,000 profit

NESBØ MASKIN OG TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESBØ MASKIN OG TRANSPORT AS

Who owns NESBØ MASKIN OG TRANSPORT AS?

KAY MARTIN NESBØ is the largest registered owner, with 100.0%.

What is the revenue of NESBØ MASKIN OG TRANSPORT AS?

NESBØ MASKIN OG TRANSPORT AS had revenue of NOK 2.3m in 2025.

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

Kay Martin Nesbø is registered as general manager of NESBØ MASKIN OG TRANSPORT AS.

Where is NESBØ MASKIN OG TRANSPORT AS based?

NESBØ MASKIN OG TRANSPORT AS has its business address in Aurland.

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.