biztrac. BETA
COMPANY REGISTER PROFILE
914044685 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Funeral and related activities

FCH HOLDING AS

Org. no. 914044685 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 14,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

FCH HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 914044685. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapet skal være et holding selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▼ −283 %
Equity
NOK 14,000
▼ −24 %
Est. value
NOK 18,000

Financial health · 2025

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
-3.9%
Not satisfactory
Return on total assets
Solidity
9.9%
Weak
Equity as a share of total capital

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

Who owns FCH HOLDING AS?

FCH HOLDING AS
NOK 0 rev. · NOK −5,000 profit

FCH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FCH HOLDING AS own?

FCH HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FCH HOLDING AS

Who owns FCH HOLDING AS?

Finn Christoffersen is the largest registered owner, with 100.0%.

What is the revenue of FCH HOLDING AS?

FCH HOLDING AS had revenue of NOK 0 in 2025.

Where is FCH HOLDING AS based?

FCH HOLDING AS has its business address in Drammen.

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.