BIZTRAC BETA
Activities of adventure companies

SIGDAL OFFROAD EVENTS AS

Org. no. 925695475 Limited company (AS) Sigdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 71,000
Operating profit NOK 7,000
Equity NOK 87,000
Incorporated 2020
Share capital NOK 30,000

SIGDAL OFFROAD EVENTS AS is registered as a limited company in Sigdal, Buskerud with organisation number 925695475. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Opplevelsessenter med utleie av motorisert kjøretøy, kjøring i tilpassede traseer, events og arrangementer, og annet som naturlig hører sammen med dette. Herunder også deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 71,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 71,000
Operating profit
NOK 7,000
Equity
NOK 87,000
Est. value
NOK 68,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SIGDAL OFFROAD EVENTS AS?

EILEV RONNY HALSTENRUD
SIGDAL OFFROAD EVENTS AS
NOK 71,000 rev. · NOK 7,000 profit

SIGDAL OFFROAD EVENTS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIGDAL OFFROAD EVENTS AS

Who owns SIGDAL OFFROAD EVENTS AS?

EILEV RONNY HALSTENRUD is the largest registered owner, with 50.0%.

What is the revenue of SIGDAL OFFROAD EVENTS AS?

SIGDAL OFFROAD EVENTS AS had revenue of NOK 71,000 in 2025.

Where is SIGDAL OFFROAD EVENTS AS based?

SIGDAL OFFROAD EVENTS AS has its business address in Eggedal.

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.