BIZTRAC BETA
Activities of excursion and event organisers

TYNSET EVENT AS

Org. no. 928126498 Limited company (AS) Tynset Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 54,000
Equity NOK 557,000
Incorporated 2021
Employees 11
Share capital NOK 30,000

TYNSET EVENT AS is registered as a limited company in Tynset, Innlandet with organisation number 928126498. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2021 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arrangere alle typer aktiviteter og sammenkomster for alle bransjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 54,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 54,000
Equity
NOK 557,000
Est. value
NOK 497,000

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.8%
Good
Equity as a share of total capital

Who owns TYNSET EVENT AS?

KVIKNE AUTOSENTER AS
TYNSET EVENT AS
NOK 3.7m rev. · NOK 54,000 profit

TYNSET EVENT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TYNSET EVENT AS own?

TYNSET EVENT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TYNSET EVENT AS

Who owns TYNSET EVENT AS?

KVIKNE AUTOSENTER AS is the largest registered owner, with 50.0%.

What is the revenue of TYNSET EVENT AS?

TYNSET EVENT AS had revenue of NOK 3.7m in 2025.

Who is the general manager of TYNSET EVENT AS?

Valon Salihu is registered as general manager of TYNSET EVENT AS.

Where is TYNSET EVENT AS based?

TYNSET EVENT AS has its business address in Tynset.

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.