BIZTRAC BETA
Wholesale of chemical products

SVEA FYRVERKERIER AS

Org. no. 980029794 Limited company (AS) Lillestrøm Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 56.1m
Operating profit NOK 6.8m
Equity NOK 52.7m
Incorporated 1998
Employees 11
Share capital NOK 900,000

SVEA FYRVERKERIER AS is registered as a limited company in Lillestrøm, Akershus with organisation number 980029794. The business is classified under wholesale of chemical products (NACE 46.850). The company was incorporated in 1998 and has 11 registered employees. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Import og grossistvirksomhet med tyngdepunkt på fyrverkeri samt investeringer og deltakelse i andre selskap og annet som kan settes i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 56.1m in revenue and NOK 6.8m in operating profit.

Key figures · 2024

Revenue
NOK 56.1m
Operating profit
NOK 6.8m
Equity
NOK 52.7m
Est. value
NOK 50.3m

Financial health · 2024

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

Who owns SVEA FYRVERKERIER AS?

LAIDBACK HOLDING AS
SVEA FYRVERKERIER AS
NOK 56.1m rev. · NOK 6.8m profit

SVEA FYRVERKERIER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEA FYRVERKERIER AS

Who owns SVEA FYRVERKERIER AS?

LAIDBACK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SVEA FYRVERKERIER AS?

SVEA FYRVERKERIER AS had revenue of NOK 56.1m in 2024.

Who is the general manager of SVEA FYRVERKERIER AS?

Sven Anders Bertil Sture is registered as general manager of SVEA FYRVERKERIER AS.

Where is SVEA FYRVERKERIER AS based?

SVEA FYRVERKERIER AS has its business address in Kjeller.

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.