biztrac. BETA
COMPANY REGISTER PROFILE
932524899 ORG. NO. 2026 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of wood, construction materials and sanitary equipment

FIRESEAL AS

Org. no. 932524899 Limited company (AS) Færder Incorporated 2023 Active
Ownership graph ↗
Revenue 2026 NOK 5.0m
Operating profit NOK 636,000
Equity NOK 488,000
Incorporated 2023
Share capital NOK 30,000

FIRESEAL AS is registered as a limited company in Færder, Vestfold with organisation number 932524899. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Handel med produkter og tilhørende tjenester innen passiv brannvern.”. The most recent filed accounts, for the 2026 financial year, show NOK 5.0m in revenue and NOK 636,000 in operating profit.

Former names: NFH 231124 AS

Key figures · 2026

Revenue
NOK 5.0m
▲ +90 %
Operating profit
NOK 636,000
▲ +212 %
Equity
NOK 488,000
▲ +1119 %
Est. value
NOK 1.3m

Financial health · 2026

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
22.8%
Very good
Return on total assets
Solidity
17.4%
Satisfactory
Equity as a share of total capital

Who owns FIRESEAL AS?

FIRESEAL AB SE
FIRESEAL AS
NOK 5.0m rev. · NOK 636,000 profit

FIRESEAL AS has 1 registered shareholder:

  • FIRESEAL AB 100.0%
All shareholders and roles →

Frequently asked questions about FIRESEAL AS

Who owns FIRESEAL AS?

FIRESEAL AB is the largest registered owner, with 100.0%.

What is the revenue of FIRESEAL AS?

FIRESEAL AS had revenue of NOK 5.0m in 2026.

Who is the general manager of FIRESEAL AS?

Christoffer Kenneth Bergum Nyman is registered as general manager of FIRESEAL AS.

Where is FIRESEAL AS based?

FIRESEAL AS has its business address in Nøtterøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.