BIZTRAC BETA
Non-scheduled passenger transport by road

HELGELAND TUR BUSS AS

Org. no. 917445737 Limited company (AS) Hemnes Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK −44,000
Equity NOK 398,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−44k kr).

HELGELAND TUR BUSS AS is registered as a limited company in Hemnes, Nordland with organisation number 917445737. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Turbussvirksomhet, lastebiltransport og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK −44,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK −44,000
Equity
NOK 398,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns HELGELAND TUR BUSS AS?

GEIR WILLY NYGÅRD
HELGELAND TUR BUSS AS
NOK 2.2m rev. · NOK −44,000 profit

HELGELAND TUR BUSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELGELAND TUR BUSS AS

Who owns HELGELAND TUR BUSS AS?

GEIR WILLY NYGÅRD is the largest registered owner, with 100.0%.

What is the revenue of HELGELAND TUR BUSS AS?

HELGELAND TUR BUSS AS had revenue of NOK 2.2m in 2024.

Who is the general manager of HELGELAND TUR BUSS AS?

Geir Willy Nygård is registered as general manager of HELGELAND TUR BUSS AS.

Where is HELGELAND TUR BUSS AS based?

HELGELAND TUR BUSS AS has its business address in Korgen.

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.