BIZTRAC BETA
Wholesale of other food

FINDAL & KROGH AS

Org. no. 971153865 Limited company (AS) Drammen Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 174.0m
Operating profit NOK 3.1m
Equity NOK 13.0m
Incorporated 1994
Employees 6
Share capital NOK 1.0m

FINDAL & KROGH AS is registered as a limited company in Drammen, Buskerud with organisation number 971153865. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 1994 and has 6 registered employees. Registered share capital is NOK 1.0m, divided into 10 shares. The company's stated purpose is: “Import. Agenturviksomhet og salg av varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 174.0m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 174.0m
Operating profit
NOK 3.1m
Equity
NOK 13.0m
Est. value
NOK 14.1m

Financial health · 2024

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.5%
Good
Equity as a share of total capital

Who owns FINDAL & KROGH AS?

3K HOLDING AS
FINDAL & KROGH AS
NOK 174.0m rev. · NOK 3.1m profit

FINDAL & KROGH AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FINDAL & KROGH AS own?

FINDAL & KROGH AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

FINDAL & KROGH AS er morselskap for 1 datterselskap:

Frequently asked questions about FINDAL & KROGH AS

Who owns FINDAL & KROGH AS?

3K HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of FINDAL & KROGH AS?

FINDAL & KROGH AS had revenue of NOK 174.0m in 2024.

Who is the general manager of FINDAL & KROGH AS?

Jarle Findal is registered as general manager of FINDAL & KROGH AS.

Where is FINDAL & KROGH AS based?

FINDAL & KROGH 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 15.06.2026.

Report a problem

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