BIZTRAC BETA
Retail sale of other new goods

ØYA FYRVERKERI AS

Org. no. 912902757 Limited company (AS) Vefsn Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 149,000
Operating profit NOK −9,000
Equity NOK 91,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

ØYA FYRVERKERI AS is registered as a limited company in Vefsn, Nordland with organisation number 912902757. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av fyrverkeri samt eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 149,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 149,000
Operating profit
NOK −9,000
Equity
NOK 91,000
Est. value
NOK 92,000

Financial health · 2025

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

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

Who owns ØYA FYRVERKERI AS?

EMIL STUVLAND GUNNARSSON
ØYA FYRVERKERI AS
NOK 149,000 rev. · NOK −9,000 profit

ØYA FYRVERKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYA FYRVERKERI AS

Who owns ØYA FYRVERKERI AS?

EMIL STUVLAND GUNNARSSON is the largest registered owner, with 100.0%.

What is the revenue of ØYA FYRVERKERI AS?

ØYA FYRVERKERI AS had revenue of NOK 149,000 in 2025.

Who is the general manager of ØYA FYRVERKERI AS?

Emil Stuvland Gunnarsson is registered as general manager of ØYA FYRVERKERI AS.

Where is ØYA FYRVERKERI AS based?

ØYA FYRVERKERI AS has its business address in Mosjøen.

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.