BIZTRAC BETA
Activities of excursion and event organisers

NORGES RÅESTE BAKKELØP AS

Org. no. 918640924 Limited company (AS) Harstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 458,000
Equity NOK 955,000
Incorporated 2017
Share capital NOK 30,000

NORGES RÅESTE BAKKELØP AS is registered as a limited company in Harstad, Troms with organisation number 918640924. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Motorsports arrangement herunder utleie av utstyr, deltagelse i andre selskaper og det som naturlig hører herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 458,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 458,000
Equity
NOK 955,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns NORGES RÅESTE BAKKELØP AS?

JAN HELGE NILSSEN
NORGES RÅESTE BAKKELØP AS
NOK 3.3m rev. · NOK 458,000 profit

NORGES RÅESTE BAKKELØP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORGES RÅESTE BAKKELØP AS

Who owns NORGES RÅESTE BAKKELØP AS?

JAN HELGE NILSSEN is the largest registered owner, with 65.0%.

What is the revenue of NORGES RÅESTE BAKKELØP AS?

NORGES RÅESTE BAKKELØP AS had revenue of NOK 3.3m in 2025.

Who is the general manager of NORGES RÅESTE BAKKELØP AS?

Jan Helge Nilssen is registered as general manager of NORGES RÅESTE BAKKELØP AS.

Where is NORGES RÅESTE BAKKELØP AS based?

NORGES RÅESTE BAKKELØP AS has its business address in Harstad.

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.