biztrac. BETA
COMPANY REGISTER PROFILE
913341147 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

A/S Katfos Fabrikker

Org. no. 913341147 Limited company (AS) Drammen Incorporated 1898 Active
Ownership graph ↗
Operating profit NOK −604,000
Equity NOK 15.8m
Incorporated 1898
Share capital NOK 1.0m

Signals

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

A/S Katfos Fabrikker is registered as a limited company in Drammen, Buskerud with organisation number 913341147. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1898. Registered share capital is NOK 1.0m, divided into 1986 shares. The company's stated purpose is: “Fabrikkdrift, handels- og utleievirksomhet, ervervelse og salg av interesser i andre foretagender samt for ovennevnte tilhørende og beslektet virksomhet. I tillegg, handel med aksjer og verdipapirer, herunder lånefinansierte investeringer med verdipapirer og valuta.”.

Key figures · 2025

Operating profit
NOK −604,000
▼ −3 %
Equity
NOK 15.8m
▲ +33 %
Est. value
NOK 34.2m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
15.9%
Very good
Return on total assets
Solidity
37.2%
Good
Equity as a share of total capital

Who owns A/S Katfos Fabrikker?

A/S Katfos Fabrikker
· NOK −604,000 profit

A/S Katfos Fabrikker has 1 registered shareholder:

All shareholders and roles →

Which companies does A/S Katfos Fabrikker own?

A/S Katfos Fabrikker holds stakes in 16 companies:

See the full ownership structure →

Group structure

A/S Katfos Fabrikker er morselskap for 4 datterselskaper:

Frequently asked questions about A/S Katfos Fabrikker

Who owns A/S Katfos Fabrikker?

S & B NEDBERG AS is the largest registered owner, with 100.0%.

Where is A/S Katfos Fabrikker based?

A/S Katfos Fabrikker 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.