biztrac. BETA
COMPANY REGISTER PROFILE
923798501 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of adventure companies

HAMAREN EVENT AS

Org. no. 923798501 Limited company (AS) Fyresdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 7,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

HAMAREN EVENT AS is registered as a limited company in Fyresdal, Telemark with organisation number 923798501. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby spenningsaktiviteter til fastboende og turister i Fyresdal.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▲ +4 %
Equity
NOK 7,000
▼ −40 %
Est. value
NOK 9,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-49.8%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns HAMAREN EVENT AS?

HAMAREN EVENT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAMAREN EVENT AS

Who owns HAMAREN EVENT AS?

Sigurd Skomedal is the largest registered owner, with 34.0%.

What is the revenue of HAMAREN EVENT AS?

HAMAREN EVENT AS had revenue of NOK 0 in 2025.

Who is the general manager of HAMAREN EVENT AS?

Espen Storebø Valseth is registered as general manager of HAMAREN EVENT AS.

Where is HAMAREN EVENT AS based?

HAMAREN EVENT AS has its business address in Fyresdal.

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.