BIZTRAC BETA
Drying and salting of fish

HANS FAUSKE & SØNN AS

Org. no. 857459512 Limited company (AS) Giske Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 465,000
Equity NOK 4.3m
Incorporated 1990
Employees 11
Share capital NOK 100,000

HANS FAUSKE & SØNN AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 857459512. The business is classified under drying and salting of fish (NACE 10.201). The company was incorporated in 1990 and has 11 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Produksjon av salt-, tørr, og klippfisk. Selskapet kan engasjere seg i andre virksomheter, enten direkte eller ved kjøp av aksjer, parter eller på annen måte. ”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 465,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 465,000
Equity
NOK 4.3m
Est. value
NOK 4.2m

Financial health · 2024

Liquidity
2.18
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.2%
Very good
Equity as a share of total capital

Who owns HANS FAUSKE & SØNN AS?

RANDI MARIA FAUSKE BLINDHEIM
HANS FAUSKE & SØNN AS
NOK 3.4m rev. · NOK 465,000 profit

HANS FAUSKE & SØNN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HANS FAUSKE & SØNN AS

Who owns HANS FAUSKE & SØNN AS?

RANDI MARIA FAUSKE BLINDHEIM is the largest registered owner, with 50.0%.

What is the revenue of HANS FAUSKE & SØNN AS?

HANS FAUSKE & SØNN AS had revenue of NOK 3.4m in 2024.

Who is the general manager of HANS FAUSKE & SØNN AS?

Hans Frode Fauske is registered as general manager of HANS FAUSKE & SØNN AS.

Where is HANS FAUSKE & SØNN AS based?

HANS FAUSKE & SØNN AS has its business address in Valderøya.

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.