BIZTRAC BETA
Other support activities to arts and performing arts

LYN&TORDEN EVENT AS

Org. no. 922250804 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 45.8m
Operating profit NOK 2.3m
Equity NOK 4.6m
Incorporated 2019
Employees 7
Share capital NOK 30,000

LYN&TORDEN EVENT AS is registered as a limited company in Bærum, Akershus with organisation number 922250804. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2019 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Planlegging og gjennomføring av firmaarrangementer, impresariovirksomhet, samt kommunikasjons- og rådgivningstjenester knyttet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 45.8m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 45.8m
Operating profit
NOK 2.3m
Equity
NOK 4.6m
Est. value
NOK 12.7m

Financial health · 2025

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

Who owns LYN&TORDEN EVENT AS?

MARTIN VINJE AS
LYN&TORDEN EVENT AS
NOK 45.8m rev. · NOK 2.3m profit

LYN&TORDEN EVENT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYN&TORDEN EVENT AS

Who owns LYN&TORDEN EVENT AS?

MARTIN VINJE AS is the largest registered owner, with 33.4%.

What is the revenue of LYN&TORDEN EVENT AS?

LYN&TORDEN EVENT AS had revenue of NOK 45.8m in 2025.

Who is the general manager of LYN&TORDEN EVENT AS?

Martin Vinje is registered as general manager of LYN&TORDEN EVENT AS.

Where is LYN&TORDEN EVENT AS based?

LYN&TORDEN EVENT AS has its business address in Fornebu.

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.