BIZTRAC BETA
Retail sale of other new goods

ROMERIKE FYRVERKERI AS

Org. no. 836610962 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 565,000
Operating profit NOK 126,000
Equity NOK 53,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-27.

ROMERIKE FYRVERKERI AS is registered as a limited company in Lillestrøm, Akershus with organisation number 836610962. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Handel med fyrverkeri og andre produkter som hører samen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 565,000 in revenue and NOK 126,000 in operating profit.

Key figures · 2025

Revenue
NOK 565,000
Operating profit
NOK 126,000
Equity
NOK 53,000
Est. value
NOK 390,000

Financial health · 2025

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

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

Who owns ROMERIKE FYRVERKERI AS?

BEZO AS
ROMERIKE FYRVERKERI AS
NOK 565,000 rev. · NOK 126,000 profit

ROMERIKE FYRVERKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMERIKE FYRVERKERI AS

Who owns ROMERIKE FYRVERKERI AS?

BEZO AS is the largest registered owner, with 100.0%.

What is the revenue of ROMERIKE FYRVERKERI AS?

ROMERIKE FYRVERKERI AS had revenue of NOK 565,000 in 2025.

Who is the general manager of ROMERIKE FYRVERKERI AS?

Bjørn Hansen is registered as general manager of ROMERIKE FYRVERKERI AS.

Where is ROMERIKE FYRVERKERI AS based?

ROMERIKE FYRVERKERI AS has its business address in Skedsmokorset.

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.