BIZTRAC BETA
Other support activities to arts and performing arts

NORSK SPEKEMATFESTIVAL AS

Org. no. 916861915 Limited company (AS) Tynset Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 682,000
Operating profit NOK 96,000
Equity NOK 491,000
Incorporated 2016
Share capital NOK 530,000

NORSK SPEKEMATFESTIVAL AS is registered as a limited company in Tynset, Innlandet with organisation number 916861915. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2016. Registered share capital is NOK 530,000, divided into 530 shares. The company's stated purpose is: “Arrangere spekematfestival samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 682,000 in revenue and NOK 96,000 in operating profit.

Key figures · 2024

Revenue
NOK 682,000
Operating profit
NOK 96,000
Equity
NOK 491,000
Est. value
NOK 697,000

Financial health · 2024

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

Who owns NORSK SPEKEMATFESTIVAL AS?

TYNSET EVENT AS
NORSK SPEKEMATFESTIVAL AS
NOK 682,000 rev. · NOK 96,000 profit

NORSK SPEKEMATFESTIVAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK SPEKEMATFESTIVAL AS

Who owns NORSK SPEKEMATFESTIVAL AS?

TYNSET EVENT AS is the largest registered owner, with 100.0%.

What is the revenue of NORSK SPEKEMATFESTIVAL AS?

NORSK SPEKEMATFESTIVAL AS had revenue of NOK 682,000 in 2024.

Who is the general manager of NORSK SPEKEMATFESTIVAL AS?

Valon Salihu is registered as general manager of NORSK SPEKEMATFESTIVAL AS.

Where is NORSK SPEKEMATFESTIVAL AS based?

NORSK SPEKEMATFESTIVAL 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.