biztrac. BETA
COMPANY REGISTER PROFILE
928046079 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Sports activities n.e.c.

RACEDAYS TIMING AS

Org. no. 928046079 Limited company (AS) Hole Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 185,000
Equity NOK 262,000
Incorporated 2021
Share capital NOK 30,000

RACEDAYS TIMING AS is registered as a limited company in Hole, Buskerud with organisation number 928046079. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Yte tidtaking- og resultattjenester, samt salg av varer og tjenester til arrangører og deltakere på idrettsarrangement.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 185,000 in operating profit.

Former names: LØPSKONSULT AS

Key figures · 2025

Revenue
NOK 1.0m
▲ +50 %
Operating profit
NOK 185,000
▲ +431 %
Equity
NOK 262,000
▲ +121 %
Est. value
NOK 835,000

Financial health · 2025

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
61.1%
Very good
Return on total assets
Solidity
58.9%
Very good
Equity as a share of total capital

Who owns RACEDAYS TIMING AS?

RACEDAYS TIMING AS
NOK 1.0m rev. · NOK 185,000 profit

RACEDAYS TIMING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RACEDAYS TIMING AS

Who owns RACEDAYS TIMING AS?

Tom-Erik Lukkedal is the largest registered owner, with 100.0%.

What is the revenue of RACEDAYS TIMING AS?

RACEDAYS TIMING AS had revenue of NOK 1.0m in 2025.

Who is the general manager of RACEDAYS TIMING AS?

Tom-Erik Lukkedal is registered as general manager of RACEDAYS TIMING AS.

Where is RACEDAYS TIMING AS based?

RACEDAYS TIMING AS has its business address in Røyse.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.