BIZTRAC BETA
Activities of excursion and event organisers

FJORD CLASSICS AS

Org. no. 920572367 Limited company (AS) Sandefjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 16,000
Equity NOK 17,000
Incorporated 2018
Share capital NOK 30,000

FJORD CLASSICS AS is registered as a limited company in Sandefjord, Vestfold with organisation number 920572367. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av den årlige, internasjonale kammermusikkfestivalen "Fjord Classics" som finner sted på sommerstid i Sandefjord.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 16,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 16,000
Equity
NOK 17,000
Est. value
NOK 76,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.5%
Weak
Equity as a share of total capital

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

Who owns FJORD CLASSICS AS?

LARS ANDERS TOMTER
FJORD CLASSICS AS
NOK 2.7m rev. · NOK 16,000 profit

FJORD CLASSICS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJORD CLASSICS AS

Who owns FJORD CLASSICS AS?

LARS ANDERS TOMTER is the largest registered owner, with 50.0%.

What is the revenue of FJORD CLASSICS AS?

FJORD CLASSICS AS had revenue of NOK 2.7m in 2024.

Who is the general manager of FJORD CLASSICS AS?

Sean Anthony Willumsen Lewis is registered as general manager of FJORD CLASSICS AS.

Where is FJORD CLASSICS AS based?

FJORD CLASSICS AS has its business address in Sandefjord.

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.